From technical tasks to strategic vision

Mikk joined a KoThinker mastermind group as a strong technical product manager. He shipped fast, ran tight backlogs, and kept his squad on the rails. The thing he could not shake was a quieter feeling — that he was operating inside the strategy instead of shaping it.

The starting point

On paper, things looked good. The team delivered. Stakeholders were happy. But Mikk's week was almost entirely reactive: tickets, reviews, meetings, unblocking. The "big picture" work — where his product was going in 12 months, what bets actually mattered, what to stop doing — kept sliding to "next week."

He had read the books. He knew what good product strategy looked like. The bottleneck was not knowledge. It was follow-through under pressure.

The shift

In the mastermind group, Mikk picked one shift and committed to it: move from execution-led to vision-led product leadership. Not as a slogan — as a weekly practice.

Three things changed how he ran his week:

• A visible journey. Instead of a vague intention, the shift had concrete checkpoints. Each week he could see where he was, what was next, and what "done" looked like.
• One next action, not ten. Between sessions, he stopped trying to boil the ocean. The work was always one specific, small move he could finish before the next call.
• Five other people in the same fight. Peers who were not his team, not his manager, not his coach — just other leaders pushing through the same messy middle. That is what made it stick when nothing else had.

What changed

Within a few months, the shape of Mikk's week was different. Strategy stopped being a quarterly artefact and became something he worked on every week. Conversations with leadership changed — less "here is the status," more "here is where we should go and why." His squad felt the difference too: fewer reactive sprints, clearer bets, sharper trade-offs.

The technical PM did not disappear. That muscle was still there. But it stopped being the only one he used.

Why it worked

Mikk did not need another framework. He needed a way to make the shift land — visible enough to track, small enough to act on between meetings, and witnessed by peers who would notice if he stopped showing up. That combination is what KoThinker is now built around.