When I first joined Kegate, I assumed I could just roll up, plug in, and get to work.
I was wrong.
Not because the people weren’t welcoming, or the work wasn’t exciting — it was. But within a few weeks, I realised I was making quiet missteps that weren’t obvious on the surface, but definitely slowed things down. I learned the hard way that even in fast-moving companies like Kegate, culture and process matter just as much as code or product knowledge.
So here’s what I wish someone had told me back then — and what I now pass on to anyone new stepping into a team like ours.
Don’t Confuse Collaboration with Control
At Kegate, decision-making isn’t a free-for-all. There’s space for ideas, yes — loads of it. But once a direction is agreed, the expectation is simple: we move. I had a habit of circling back on decisions that were already settled. Not to be difficult, but to be thorough. Turns out, that can stall momentum fast. Lesson one: input early, align quickly, then follow through.
Role Clarity Isn’t Optional
I used to think flexibility meant taking on anything that came my way. But here, clarity is power. Kegate works best when people know what they’re accountable for — and equally, what’s not theirs to chase. Early on, I found myself half-owning things that weren’t mine, and missing things that were. Now, I check: what’s expected of me? What am I driving? What am I supporting?
Standups Are Just the Surface
We do daily standups like most teams, but if that’s the only time you’re communicating, you’re probably missing things. I once assumed “no questions” meant “no problems” — until someone flagged that I hadn’t followed up on a blocker. That’s when I realised: if it’s not clear, don’t wait. Drop a message. Jump on a call. Progress doesn’t happen on autopilot.
We Do Sprints — Even If the Board Looks Like Kanban
At first glance, our board looked fluid, like a classic Kanban setup. So I figured maybe we weren’t running sprints. That assumption caused more confusion than I’d like to admit. Truth is, Kegate’s delivery is structured, even when it looks flexible. The board’s just a view — the rhythm underneath it matters more. Always ask how delivery flows before assuming you know it.
Silence Is a Signal — And Not a Good One
At Kegate, no one wants to chase you. And “no update” is rarely a good update. There were weeks where I kept my head down, thinking I’d just emerge with a finished piece of work. But the team needed visibility, not surprises. Now, I make a habit of over-communicating. A short update. A quick Slack message. Anything to keep momentum visible.
Your Words Matter — Even in Slack
This one stung. I once dropped a quick “didn’t have time yet” in reply to a teammate’s question. I didn’t mean it in a dismissive way — I was just under pressure. But it came off cold, and it caused tension I didn’t even realise until days later. At Kegate, tone matters. You can be honest and constructive. That balance goes a long way.
Actions Win, Every Time
The best advice I got? Don’t worry about saying the right thing. Just show up. Contribute. Be consistent. At Kegate, progress speaks louder than politeness, louder than over-explaining, louder than anything. If you’re getting things done and moving the team forward, people will notice.
My thoughts
Kegate moves fast and expects people to move with it. But that doesn’t mean rushing. It means staying sharp, staying aligned, and acting like you’re part of something bigger than your own ticket list. That’s the mindset that works here.
And if you’re just joining — consider this your head start.
