Keep the customer in the room.
Customer KPIs get published where the whole team can see them, so every priority traces back to what customers actually measure us on.
Use data as the guide and conversations as the source of truth.
Data shows what is happening. Customers, sales, and support explain why. The people closest to the customer usually see a problem before it shows up in the numbers.
Measure what you can before you build what you want to measure.
Build around what you actually know. Set up measurement from the start, and let the roadmap change as the data comes in.
Start with the customer’s problem, not the technology.
AI and new platforms can help a team ship faster, but the value is the outcome the customer gets, not the technology used to get there.
Plan around real events, not the calendar.
Tie releases and reviews to what actually matters to the business: launch customers, QBRs, and board meetings.
Automate where it saves time. Keep people where mistakes are costly.
A human review step isn’t always a bottleneck. Where a mistake would reach customers, it’s the check that protects them.
Mission alignment before roadmap.
Before a roadmap gets discussed, the team needs to understand why the work matters. Every roadmap item should trace back to the product’s purpose and the customer it serves.
Alignment comes before accountability.
Getting people to nod in a roadmap review is easy. Real alignment takes time, curiosity, and room to disagree. Once it’s real, follow-through is straightforward because everyone has committed to the same outcome.
Make progress visible.
People tolerate problems they can see and lose confidence in the ones they can’t. Publish the roadmap and the customer KPIs so everyone knows where things stand.
Remove blockers before you optimize.
Find what is keeping the team from shipping and remove it. Speed follows. Optimization comes after.
Development plans anchored to the future, not the current role.
Personal development plans get built around where someone wants to be in three years, not the title they hold today — a roadmap for a person, the same discipline as a roadmap for a product.
Weekly 1:1s that track progress against that trajectory.
Not status updates. A standing check against the plan we actually built together, so drift gets caught in weeks, not at the next review cycle.
Curiosity before intervention.
When something’s off, the first move is a question, not a correction. Most performance problems are context problems, and you only find that out by asking.