The trip#
The Scratchcode team made it to Cape Coast for a two-day offsite — part sightseeing, part strategy, mostly just real talk. We've been working closely for months but hadn't properly gotten off-screen together, so this was overdue.
The drive down was three hours of playlist debates and half-finished ideas. The kind of conversations that don't happen on a Slack thread.
What made it useful#
It wasn't a structured workshop. We spent time at Cape Coast Castle, had dinner by the water, and somewhere between the history lesson and the argument about what Scratchcode should be doing in the next 18 months, we actually aligned on some things we hadn't made explicit before.
The big one: what kind of team are we building? Not just the product — the people, the pace, the culture. Walking through a place with that much weight to it has a way of putting "what are we actually doing here" into sharper focus.
What I took back#
- A clearer picture of where I want to sit in this team over the next year
- Better understanding of what the team needs from me specifically
- A reminder that alignment comes from conversations, not documents
Why this counts as a win
Wins aren't only production fixes. Showing up for team moments, staying curious about the people you build with, and taking time to think about direction — that's part of the job too.