Planning Dashboard
A white-label planning calendar and task tracker
Our team needed a way to plan and track work without asking non-technical teammates to work directly in GitHub. I started with a simpler interface on top of GitHub Projects, then expanded it into a planning and execution tool of its own.
The key decision was separating planning from execution while keeping them connected. This let teams work at different levels of detail without losing the context between a campaign, its planning and the actual production work.
Rather than imposing a fixed workflow, I designed the system to adapt to different teams. Views, filters, layers, statuses and other structures can be configured without changing the underlying product.
One calendar, everyone sees the same plan
I wanted one place where the team could see what was happening without having to translate between different tools and spreadsheets.
Same work, different view
Not everyone needs the same level of detail. The underlying work stays connected while people can look at it in the way that makes sense for them.
Make the workflow fit us
I didn’t want to copy another team’s process just because the software expected it. The board follows how we actually move work through the team.
Keep the detail connected
Planning is only useful if you can get from the big picture to the actual work. Tasks and milestones stay connected to the plan instead of becoming another list somewhere else.
Don’t hardcode the team
Teams change, and the way they work changes with them. I made the structure configurable so changing a workflow doesn’t mean changing the product.
Different people need different views
A social team, a designer and a manager don’t need to see the same thing. Layers let the same system show each person what is relevant to them.
Build what we actually needed
We didn’t need another huge SaaS platform. We needed a tool that fit our team, our workflow and our budget. So I built that instead.
Useful outside the team too
External people sometimes need to see progress without getting access to everything. Sharing became part of the system rather than another workaround.
