Problem-Led Creative Leadership
Give teams the problem and context, then let specialists create the solution
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 95%
Problem-Led Creative Leadership makes the leader responsible for context and enablement rather than for issuing every solution. The leader explains the problem, why it matters to the customer and the rest of the company, and any genuine constraints. Specialists with different perspectives then work out the solution because their combined judgment is the reason they were hired. Decisions remain with the people closest to the work, while systems provide information and coordination without dictating action. Meetings happen only when a group genuinely needs to resolve something. The mechanism preserves both alignment and creativity: wider context prevents local decisions from harming the whole, and autonomy prevents hierarchy from wasting the team's brains. Leadership succeeds when people have what they need and are free to surprise the organisation with a better answer.
Origin
Petty linked Blackmagic Design's culture to his television engineering background, where varied specialists worked together and leadership supported their contribution. Extracted from The Foundr Podcast.
Core principles
- 01Treat leadership as service to the team
- 02Describe problems instead of prescribing solutions
- 03Give decision-makers the wider context they need
- 04Place decisions with the person closest to the work
- 05Use systems to support people, not dominate them
How to run it
- 1
Frame the problem
State what is wrong or what outcome is needed without embedding your preferred solution. Make the problem specific enough for specialists to engage with it.
Pro tip Use problems to invite other people's brains into the work.
Watch out A disguised instruction does not create genuine problem-solving room.
- 2
Supply the wider context
Explain how the work interacts with the product, customer, and other groups. Give the person closest to the decision enough information to understand those effects.
Watch out Autonomy without context can optimise one part at the expense of the whole.
- 3
Connect distinct specialists
Bring together the different disciplines required by the problem. Make their mutual dependence visible through an ambitious shared product.
Pro tip A stretching product can help specialists value one another's contribution.
Watch out Several copies of the same perspective do not make a multidisciplinary team.
- 4
Enable the decision-maker
Provide tools, information, access, and support, then let the person doing the work make the relevant decision. Avoid adding hierarchy merely to approve it.
Watch out Intervening with a solution too early wastes the expertise you assembled.
- 5
Resolve through direct conversation
Move between the groups and discuss concrete issues as they appear. Convene a meeting only when bringing a group together is necessary to work something out.
Pro tip Use the product and the problem as the shared reference point.
Watch out Recurring status meetings consume time without necessarily resolving work.
In the wild
Petty said that in meetings he tries to describe what the company needs in terms of problems rather than solutions. He said watching talented people engage with the problem can reveal how much capability is in the room and produce an answer he did not specify.
→ Specialists contribute their own judgment instead of implementing the CEO's preselected answer.
Petty argued that the person doing the work should make the decision because that person knows the immediate conditions. The leader's job is to provide the bigger picture so the local choice accounts for effects on the rest of the company.
→ Decision authority stays close to the work while remaining informed by company-wide context.
Common mistakes
Embedding the answer in the problem
Prescribing a solution prevents the team from applying perspectives the leader does not have.
Delegating without context
The person closest to the work still needs to understand how the decision affects the wider product and organisation.
Using meetings as routine control
Petty treats meetings as a tool for resolving a real issue, not a default claim on everyone's time.
Is it for you?
Best for
It is best for capable specialists whose different perspectives must combine into one product.
Not ideal for
It is not ideal when the team lacks the context or competence needed to make the delegated decision safely.
From the transcript
“your job is to enable everyone else to do their thing”
“you do tend to try and describe the world of what we need to be doing in forms of problems not solutions”
“your job is to give him the bigger picture”
From the episode
236: Bootstrapping a $300M Cinema Company, With Grant Petty of Blackmagic Design
Grant Petty