I spent a bit of time putting together a “roadmap” of sorts for the month of August, 2020 and it looks like so:
It’s not sexy but it gets the job done. I do this for a number of reasons:
Alignment— My team knows who’s working on what and when I expect those things to be done.
Dependencies— It allows us to see the (inter)dependencies of our work that could create blockers if we do not adequately prepare.
A Canonical Target— This allows us to have something concrete to discuss and talk about as we build each week. This canonical reference will give us common language and timeline.
This is just a conversation and dialogue-starter, not a hard-and-fast mandate that I’ve given my team. Like most things in life, roadmaps are effectively “best guess” scenarios that will become more clear as we walk the path.
As the CEO, I don’t have most of the answers, but, I am responsible for “setting the table” and inviting the right folks to sit down, have a chat, and figure this out together.
It’s also kind of neat to see how large we’ve grown as an operating team! In January of this year I was only one person — now, we’re quite a bit bigger.
These are exciting times.
[Originally published on Indie Hackers.]