THE METHODOLOGY
Six pillars
One connected culture
A practical foundation for seeing the work clearly, developing people’s strengths and turning a different possibility into something useful.
Read the six pillarsTHE APPROACH
Culture shapes how the work gets done
RERUT’s methodology connects what an organization is trying to achieve with how work actually happens, what people can contribute and what the evidence supports. The six pillars are enduring ways of approaching that work. They belong together: observation needs candor, strategic choices need human capability, and an imaginative proposal needs a credible way to test it. AI can support exploration and synthesis; human intent and verifiable evidence guide decisions.
The eight connected practices make those commitments practical. After an initial intake establishes shared intent and real boundaries, the work can move among them, run in parallel or return to an earlier question. There is no requirement to complete every practice in order. Requirements, decisions, implementation and documentation develop together in one evolving record.
PILLAR 01
Gemba & Perspective Analysis
What is really happening—and for whom?
Begin where the work happens. A process description explains the intended route; observation reveals the interruptions, judgment calls and informal coordination that make it function. Gemba & Perspective Analysis brings those realities into view alongside the experiences of customers, operators, technical teams, financial stakeholders and people responsible for governance. Differences between their accounts are material to investigate.
In practice
Follow a bounded piece of work through its actual handoffs. Ask people to show the information they receive, the decisions they make and the exceptions they recover from. Examine relevant artifacts and data alongside their explanations. Record successful adaptations as carefully as delays. Separate direct observation, someone’s account and the team’s interpretation so a plausible story does not quietly become an established fact.
Compare perspectives around specific decisions: who waits, who absorbs extra work, who can authorize a change and who experiences its consequences? Develop a testable explanation for the pattern, including what would contradict it. A prototype may expose a missing perspective or an incorrect diagnosis; return to the work when that happens. Protected candor helps people challenge the emerging account, especially when it reflects leadership assumptions.
What the work leaves behind
A work-as-done map, a friction and adaptation ledger, and a perspective map. Each important finding links to its evidence, unresolved questions and the person responsible for investigating them.
A short observation can capture an unusual day. Treat the sample’s limits explicitly, and avoid confusing the most visible symptom with the mechanism producing it.
PILLAR 02
Superpower Funnel
What could become a distinctive capability?
The Superpower Funnel asks which existing conditions could become distinctive, repeatable capabilities. Conversion SWOT examines strengths to amplify, weaknesses to develop or address through partnership, opportunities to explore and threats to convert or offset. Conversion is a strategic possibility to assess, not a requirement to find a positive interpretation of every problem.
In practice
Name a condition precisely, then describe the proposed conversion in terms of work the organization could perform. A strength becomes more useful when other people can learn and apply it. A weakness may justify development, a partner or a simpler operating model. For each possibility, identify the intended beneficiary, required skills, dependencies and evidence needed to show that the capability would be valuable.
Apply the Resource Rule by concentrating effort on the capabilities with a credible connection to purpose and repeatable value. Make the tradeoff visible: what receives people’s time, what waits and what stops? Human capability and operational findings should inform that choice. When conversion is not useful, choose mitigation, monitoring or responsible retirement of unnecessary work. Essential controls remain part of the design and its resource needs.
What the work leaves behind
A capability portfolio showing each proposed conversion, its rationale, owner, resource commitment and next evidence review. Include alternatives considered and the conditions for continuing, changing direction or stopping.
A promising label can hide ordinary unfinished work. Do not call something a capability until people can perform it, maintain it and explain the value it creates.
PILLAR 03
Holistic Talent & Joy Imperative
Where can people contribute their best?
Work design should consider demonstrated strengths, voluntary interests and curiosity alongside role requirements. The Holistic Talent & Joy Imperative asks where people can make a meaningful contribution and develop capability through the work itself. Joy leaves room for discovery and purposeful effort; it is not a demand for constant enthusiasm or a substitute for manageable responsibilities.
In practice
Discuss what people do well, what they want to learn and which parts of the work require energy without creating useful value. Participation in conversations about personal interests remains voluntary. Compare those accounts with the work the team actually needs to deliver. Look for arrangements that connect a real need with someone’s contribution without simply assigning more work to the most willing person.
Test a bounded change in responsibilities, pairing, decision authority or team composition. Agree what the person owns, what support is available and how existing commitments will be covered. Develop communication, connection, community, trust and respect alongside technical skill. Review the arrangement with the people affected: has the work become clearer, has capability grown and has effort merely moved to a colleague? Use their feedback to revise the experiment.
What the work leaves behind
A contribution and growth plan with agreed responsibilities, learning aims, support and a review date. A role experiment records its intended benefit, workload implications and the participant’s assessment of the change.
Strengths are not permanent boxes. Avoid reducing a person to a talent label or treating a voluntary interest as an obligation to take on extra work.
PILLAR 04
Bulletproof Psychological Safety
Can the difficult truth enter the room?
Difficult truths need a usable route into decisions. Bulletproof Psychological Safety expresses the ambition to make questions, dissent, uncertainty and mistakes discussable without humiliation or retaliation. Its working practice is protected candor with clear responsibilities and standards. “Bulletproof” names the ambition; it does not promise freedom from every interpersonal risk.
In practice
Translate that ambition into observable agreements. Ask for objections before a decision closes, distinguish a question from a refusal and let people state what they do not know. Leaders can acknowledge their own uncertainty and explain how contrary evidence changed a choice. Provide more than one way to raise concerns so participation does not depend on speaking confidently in a crowded meeting.
When a concern appears, address its substance and make the response visible to the people involved. Clarify who will investigate, what decision is pending and when the concern will be revisited. Constructive conflict still requires specific evidence, respectful conduct and accountability for agreed work. When someone is dismissed or a conversation causes harm, acknowledge what happened, agree a repair and check whether the behavior changes. These practices belong in observation, exploration and delivery alike.
What the work leaves behind
Team agreements, explicit decision responsibilities and a record of concerns and responses, with access appropriate to the information. Track unresolved questions and agreed repair actions without turning personal disclosures into performance evidence.
An invitation to speak means little if the response punishes disagreement. Assess what happens after someone challenges a decision, not just whether a leader asked for feedback.
PILLAR 05
Constraint-Free Divergent Exploration
What becomes possible when an assumption moves?
Some limits are real; others survive because no one has reopened the assumption behind them. Constraint-Free Divergent Exploration temporarily suspends inherited conventions to make different arrangements imaginable. Implementation restores practical constraints and retains ethical, legal and safety boundaries. The point is to expand the possibilities available for judgment.
In practice
State the assumption being set aside: perhaps a service must happen in a meeting, a decision must pass through one role or every request needs the same information. Give people time to explore individually before comparing ideas. Borrow a principle from another field or imagine the work in a radically different setting. Ask what that thought experiment reveals about coordination, access, information or ownership.
Bring promising principles back into the actual situation. List which constraints are fixed, which can be negotiated and which remain unverified. Compare several possibilities before committing to the most polished one. Use small prototypes or bounded operational trials to investigate the critical uncertainty. Observation can reopen exploration, and a role experiment can reveal an option the original design missed. Feed the strongest alternative into a specific Paradox Shift hypothesis.
What the work leaves behind
A possibility portfolio linking each idea to the assumption it challenges, its useful principle, restored constraints and next test. Preserve rejected options and their reasons so later evidence can reopen them.
Suspending a convention during ideation does not authorize bypassing a real obligation. Likewise, restoring constraints should prompt design work before it becomes a reason to dismiss every unfamiliar option.
PILLAR 06
Paradox Shift
Could we change the rules of the problem?
A Paradox Shift tests whether changing an operating arrangement can resolve or materially reframe a persistent tradeoff. Improving performance within the present model may still be worthwhile. The stronger claim needs evidence that a different model changes how the competing needs relate, without transferring unacceptable costs or burdens to someone else.
In practice
Name both sides of the tension and explain why the current arrangement makes them compete. Identify the mechanism the alternative would change. Write a hypothesis that connects that change to observable outcomes, and state what would count against it. Include the people who will use, operate, maintain and govern the arrangement when defining success, requirements and acceptable boundaries.
Test usefulness, adoption, affordability, reliability and controls together. Compare the trial with a documented starting point, examine exceptions and account for support work that may be easy to overlook. Decide whether to extend, revise, stop or adopt on the strength of the evidence. Before expanding, establish ownership and make requirements, implementation decisions, verification and documentation transferable. Delivery creates fresh evidence and may reopen the diagnosis or the original ambition.
What the work leaves behind
A hypothesis and decision record connecting the tradeoff, proposed mechanism, starting evidence, acceptance criteria and trial findings. Include displaced burdens, remaining uncertainty, the accountable owner and the next review.
A better headline metric cannot establish a shift by itself. Look for hidden support effort, excluded users, weakened controls and dependencies that make the arrangement difficult to sustain.
EIGHT CONNECTED PRACTICES
Follow the evidence through the work
The pillars describe the culture. These practices organize observation, decisions, experiments, and delivery. Select a practice to see what it contributes and how it connects.
HOW THE WORK MOVES
One intake
Every route stays open
Agree the need, intent and real boundaries. Then follow the evidence through the connected practices.
Learning.ONE EVOLVING RECORD
Ground truth
See work as it happens.
Combine observation, artifacts, data and people’s accounts. Notice hidden coordination, recovery and successful workarounds as well as friction.
Work-as-done map · Friction ledger · Explicit unknowns
A prototype or delivery review can send us back to observation.
SUPERPOWER FUNNEL / RESOURCE RULE
Convert what you have
Build distinctive capability
A capability map, not a scorecard. Direct effort toward useful conversions and keep necessary controls visible.
Distinctive, repeatable capability
Concentrate resources. Assign ownership. Test the value. Revisit the evidence.
FROM HYPOTHESIS TO CAPABILITY
A Paradox Shift
has to earn its name
A useful change can improve existing work. A Paradox Shift asks whether a different operating model can resolve or reframe the tradeoff itself. We test the claim against the people and system it affects.
- Purpose: Does the outcome solve a meaningful problem?
- People: Can people adopt it, access it and sustain the work?
- System: What happens to cost, reliability, controls and displaced burdens?
- Transfer: Are ownership, requirements, evidence and documentation ready to travel?
Delivery is a new observation point. Learning can reopen any part of the work.
AN EXAMPLE IN PRACTICE
Hypothetical example: faster onboarding, dependable review
This is an illustrative scenario, not a client case or a claim of measured results. Imagine a service team whose customers wait for onboarding while reviewers request missing information. Leadership describes a choice between faster access and dependable review. An initial intake defines a bounded service, the decisions the team can change and the controls that must remain.
Observation follows several requests, including exceptions. Suppose it reveals that customers answer similar questions more than once and reviewers reconstruct the same context in separate systems. A colleague also raises a concern that the proposed shortcut would remove information needed for unusual cases. The team records those observations separately from its inference: the tension may come partly from fragmented information rather than review itself.
The Superpower Funnel identifies reviewers’ diagnostic judgment as a strength worth making teachable. A reviewer who voluntarily wants to develop coaching skills helps design prompts and pairs with an onboarding colleague. Divergent exploration asks what happens if information follows the request instead of being recreated at each handoff. The resulting hypothesis is that one shared request record, with an explicit exception route, could reduce repeated work while preserving review quality.
Before a bounded trial, the team records its starting evidence and agrees to inspect elapsed time, repeated questions, missing information, exceptions and the effort required to maintain the record. Suppose routine requests become easier to complete, but exceptions still require duplicate entry and reviewers perform extra maintenance. Those hypothetical findings support a narrower decision: retain the useful prompts, revise the exception route and defer wider adoption.
The trial therefore returns the team to observation and exploration. The decision record names the unsupported part of the hypothesis, the revision owner and the evidence needed next. If a later test supports adoption, operating responsibilities, training, requirements and documentation travel with the change. The pillars remain connected throughout; a trial can end with a useful improvement even when the proposed Paradox Shift has not earned its name.
WORKING WITH RERUT
Start with the decision you need to make
An engagement can begin with a recurring difficulty, a strategic opportunity or a change that has stalled. Useful starting material includes the decision you need to make, who experiences the problem, examples of the work and the evidence already available. A finished diagnosis is not required.
Intake establishes shared intent, scope, affected people, decision authority and practical boundaries. Together, we decide what access is useful and what an initial piece of work should leave behind: a clearer diagnosis, a capability choice, a tested proposal or an operating arrangement ready to review.
The engagement follows real dependencies. Stabilization may come before exploration; a bounded improvement may be the appropriate outcome. Agree ownership and review points early, then keep decisions connected to evidence as the work develops. The aim is a result people can use, understand and carry forward.
Start a conversation