Founder role-transition map
How should a founder's work evolve as the company and leadership team scale?
Contents
A practical framework / model addressing this question: How should a founder's work evolve as the company and leadership team scale?
The question it helps answer
Use the founder role-transition map to organise the reasoning behind this question: How should a founder's work evolve as the company and leadership team scale? The working view makes company stage, founder strengths, and retained work visible so discussion can move from general opinion to a specific action or decision.
When to use it
Use the founder role-transition map when people working on personal leadership are using different mental models for company stage, founder strengths, and retained work, and that difference is changing choices or coordination.
What it is
The founder role-transition map is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are company stage, founder strengths, retained work, and delegated work. Those elements belong together because each changes how the others should be interpreted or acted on.
Core elements
Company stage
Use a small controlled set of states, define the entry and exit condition for each, and record the date of the latest change. Within the founder role-transition map, connect this entry to founder strengths so the relationship can be reviewed rather than inferred.
Founder strengths
Capture founder strengths only at the level needed to answer: How should a founder's work evolve as the company and leadership team scale? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the founder role-transition map, connect this entry to retained work so the relationship can be reviewed rather than inferred.
Retained work
Capture retained work only at the level needed to answer: How should a founder's work evolve as the company and leadership team scale? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the founder role-transition map, connect this entry to delegated work so the relationship can be reviewed rather than inferred.
Delegated work
Capture delegated work only at the level needed to answer: How should a founder's work evolve as the company and leadership team scale? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the founder role-transition map, connect this entry to new capabilities so the relationship can be reviewed rather than inferred.
New capabilities
Capture new capabilities only at the level needed to answer: How should a founder's work evolve as the company and leadership team scale? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the founder role-transition map, connect this entry to transition signals so the relationship can be reviewed rather than inferred.
Transition signals
Capture transition signals only at the level needed to answer: How should a founder's work evolve as the company and leadership team scale? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the founder role-transition map, connect this entry to new capabilities so the relationship can be reviewed rather than inferred.
See Founder role-transition map as one connected model.
Select an element to read the article’s supporting explanation while keeping the complete set visible.
Company stage
Use a small controlled set of states, define the entry and exit condition for each, and record the date of the latest change.
Continue your preview
Read more of Founder role-transition map.
Create a free account to continue this advanced article preview. Complete access is included in Pro and Team, so you can see the value before deciding to upgrade.