Who This Article Is For
- People planning a difficult project or new business
- Owners and managers defining roles in a small team
- People seeking work-related ideas from Lupin III's team
Business Planning Lessons From Lupin III’s Team and Contingency Plans
Use Lupin III’s team as a lens for business planning: prepare alternatives, define complementary roles, delegate clearly, and adapt when assumptions fail.
Published
Build a Plan With Alternatives and Clear Roles So It Can Recover
Difficult work often tempts people to rely on determination. Yet design can matter more than sheer momentum.
Alongside dramatic action, Lupin III offers lessons in anticipating events, dividing roles, and responding to surprises.
Three particularly useful ideas are:
- Avoid relying on a single storyline
- Build a team with distinct roles
- Assume events will depart from the plan
A business plan benefits from the same thinking. A design that can recover when disrupted is more useful than a claim to predict the future perfectly. Difficult challenges make this especially valuable.
A Business Plan Must Be Able to Change
Planning is sometimes treated as producing the right answer once. Real work involves changing markets, competitors, internal circumstances, and customer reactions.
Lupin's operations are interesting because they anticipate several possibilities: routes in and out, opponents' responses, betrayal, and interference. A change of circumstances therefore need not end the operation.
At work, an initial plan often changes before completion. Building around one assumption can stop everything when that assumption fails.
Consider what to change when assumptions fail so progress can continue. Prepare response options alongside predictions.
Ask during planning:
- What conditions are needed for success?
- Where might the plan fail?
- What alternatives exist?
- Who has authority over which decisions?
These questions turn a wish into something more practical. Initial design matters especially in difficult projects.
For incorporating multiple possibilities, see How to Use Scenario Planning. It describes selecting uncertain factors and preparing for different outcomes.
Team Design Lessons From Lupin's Group
The group is small, but roles are clearly divided. Knowing who handles what reduces wasted movement.
Adding people without clear responsibilities can slow decisions and blur accountability. Effective small teams cover the necessary functions without excessive overlap.
Distinct Expertise Creates Ways Forward
Lupin, Jigen, Goemon, and Fujiko have different strengths. Their different abilities work together, creating ways through difficult situations.
A business plan similarly needs functions such as:
- Seeing the whole picture and deciding
- Moving execution forward
- Gathering information
- Handling specialist problems
One person attempting everything eventually struggles. A team of similar people can also develop a narrow perspective. Build a team with no major functional gaps by combining individual abilities deliberately.
Unclear Delegation Slows the Team
Role descriptions do little if someone constantly interferes with the details. Lupin's group also illustrates trust in each other's expertise: a shared purpose leaves room for different methods.
A leader controlling everything slows local decisions. Abandoning oversight damages coordination. Clarify goals and responsibility, then delegate execution.
For example:
- The leader sets the purpose and priorities
- The responsible person chooses the method and acts
- The team agrees on intermediate check-in points
This avoids both micromanagement and neglect. Delegation affects team performance alongside ability.
Plans Show Their Quality When Things Go Wrong
Unexpected events occur despite preparation, especially in important projects. A plan's quality becomes clear when it breaks down.
Lupin's operations face interference, surprises, and changed assumptions. The story continues because the team can move again afterward.
Businesses also differ in whether they stop after the first approach fails or find another route. Preparation helps create that difference.
Plan how to recover alongside success conditions.
- What if the main sales channel becomes unavailable?
- What if the target audience responds weakly?
- Who replaces a key person who leaves?
- What remains if the budget is cut?
Considering these questions beforehand reduces panic. Recovery can be a more useful goal than expecting a plan never to fail.
Change direction promptly when needed. Excessive attachment to the first idea prevents early correction. A plan is also a reference point for revision. Teams that recognize this can be more resilient.
Practical Points for Difficult Projects
Four points make these ideas usable at work.
Write Both Success and Failure Conditions First
Imagining only success creates optimism without safeguards. State what would cause the plan to fail from the beginning. A plan increases the information available for decisions, combining the goal with the conditions that matter.
Think in Functions When Building the Team
Ask which roles are needed alongside whom to include. Is sales missing? Analysis? Fast decision-making? Identifying the function clarifies hiring and assignments.
Agree That the Plan May Change
If revision is treated as failure, employees may force the initial plan to continue. Share the conditions for reviewing it in advance so changes become easier.
Keep Purpose Separate From Method
An initial tactic can become an end in itself. If growing sales becomes protecting one campaign, the team cannot adapt. Preserve the final purpose while allowing methods to change.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To explain your business and keep its public information current as plans develop, give SpreadSite a try!
Build a website with SpreadSite →
About the Author
Thank you for reading!
I develop and operate SpreadSite, a service for creating websites from spreadsheets.
It helps people with limited time and money communicate what makes their work appealing. Consider it if you need a website! SpreadSite
Frequently Asked Questions
Q: Is a more detailed business plan always better?
A: Usefulness matters more than detail. Include alternatives for failed assumptions alongside numbers and schedules.
Q: Can a small team handle difficult projects?
A: Yes. Necessary roles, limited overlap, and quick decisions can matter more than headcount.
Q: Will frequent changes worry the team?
A: Unclear criteria are often more worrying than change itself. Shared conditions for revision help people see a change as a decision rather than confusion.
Q: How closely should a leader be involved?
A: Clarify purpose, priorities, and decision criteria, then define the scope for delegation. Controlling every method can slow execution.
Q: Can we recreate Lupin III's team at work?
A: There is no need to copy it literally. Clear roles, trust in expertise, and preparation for surprises apply across industries.
