Psychological role profile
A Plant is a neurodivergent type of contributor with pronounced divergent thinking: you see 5-7 ways to solve a problem where everyone else sees one obvious path. Your real strength is not the number of ideas, but the ability to reframe the problem itself and notice that it has been formulated incorrectly. Teams without a Plant get stuck in incremental improvements and lose competitive ground over a 2-3 year horizon; teams with one Plant and the right surrounding roles deliver qualitative breakthroughs and create new categories instead of chasing somebody else's.
Light side: superpower
- You see 5-7 options where others see one
- Not afraid to push back against the established team view
- You spot weak signals and non-obvious patterns
- You produce ideas that change the trajectory of a project
Shadow side: price of the talent
- !May lose interest in an idea once it moves into polishing and rollout
- !Often deep in your own thoughts and can miss social cues from the team
- !React painfully to early-stage criticism, before the idea is fully shaped
Unacceptable weakness
Refusing to listen to feedback and clinging to one idea even after it has clearly failed.
Work environment & motivation
Where the role thrives
Startups, R&D labs, brainstorming sessions, complex unstructured problems and creative autonomy without micromanagement.
What kills motivation
Strict regulations, repetitive routine, criticism at the idea-generation stage, rigid hierarchies.
How to manage
Give the goal, not the method - and pair the role with a Monitor Evaluator who can validate the idea.
For HR: resume markers
Look for: "innovation", "concept design", "strategic vision", "R&D", "from scratch", "patent", "first version of the product".
Avoid candidates with only routine and operational wording: "support", "execution by the manual", "regular reporting".
Leadership guide: how to manage Plant
- Set the goal and the context, not the method. "Lift retention by 20% this quarter" works; "do it like this and like this" kills the strength of the role.
- Protect 2-4 hours per week of focus time with no meetings and no channels. That window is where the most valuable contribution is born.
- Do not criticise raw ideas during the dump phase. Set a rule: at least 5 minutes of clarifying questions first, risk analysis only after that.
- Pair them immediately with a Monitor Evaluator or Completer Finisher so the idea passes through validation and delivery. Without that pairing, ideas stay on the whiteboard.
- Give them visibility when defending the decision in front of leadership - they are great at explaining "why this idea and not the three alternatives".
Tips for colleagues
- Do not ask them to take on operational routine or status meetings - you will lose their focus and they will let you down.
- When they bring a raw idea, ask 2-3 clarifying questions first and voice your doubts after that. Otherwise they will shut down.
- If a task needs a non-standard solution, hand it over with a 1-2 week horizon and stop asking for daily progress.
- When you need to ground their idea, do not reject it - ask "what do we lose if we strip this down to an MVP?" They often agree.
- Respect their need to work alone or with one close collaborator. This is not anti-social behaviour, it is their productivity mode.
Main stress triggers
Public criticism of an unfinished idea, tight deadlines and someone telling you exactly how to think.
Areas of growth & development
Three actionable steps to amplify the strengths of this role and reduce the price of its weaknesses.
Learn to present one idea at a time with a clear summary and an expected outcome. That alone will save your best ideas from being labelled "unclear".
Set a personal rule: once an idea is born, hand it off to a Monitor Evaluator or Completer Finisher for validation rather than dragging it to the finish line yourself.
Train active listening at team meetings: write down who said what before switching back to your own thoughts.
Notice the moment when you stop hearing arguments against your idea. That is the signal that ego has hijacked the process and it is time to step back.
Develop one adjacent competence (basic metrics, design or finance) - not to become a generalist, but to talk better with the people who deliver your ideas.
Team dynamics
Roles that complement
Watch out: friction zones
Similar roles: what is the difference?
Both roles work on intellectually complex problems, but in opposite directions. You generate new options, Monitor Evaluator evaluates them; you expand the solution space, they filter it. With only you on the team, ideas are not validated; with only Monitor Evaluator, there is nothing to validate. The strongest combination has both with clearly split ownership.
You and Implementer sit at opposite ends of delivery. You love uncertainty and an empty page; Implementer loves a stable plan and a clear spec. You open the task, they close it. Conflict arises when phase boundaries are blurred; the fix is an explicit hand-over with a frozen concept and a stop on changes.
