THE HARD THING ABOUT HARD THINGS

A practical guide to facing reality, protecting trust and building a company that can execute as it grows.

Combines the supplied Parts 1 and 2 with primary records and selected research. Overlapping lessons are integrated into one sequence.

Explore survival, customers, products, hiring, management systems, culture and scaling, then build your own WorkFlow.

LEADERSHIP WHEN THERE IS NO EASY ANSWER

THE CORE PROBLEM

Founders face decisions where every available option carries a cost: reduce the team, disappoint a customer, replace a loyal colleague or change the business.

Horowitz offers lessons from decisions made under pressure. Their usefulness depends on the situation. A leader still has to judge the evidence, choose a course and accept responsibility for its consequences.

WHY STANDARD ADVICE RUNS OUT

Advice such as hire great people or communicate clearly leaves difficult details unresolved.

Which strengths matter now? What should employees hear during a crisis? When should a founder change direction?

The practical work is translating a broad principle into a decision that fits the company’s customers, resources, timing and obligations.

SEPARATE FACTS FROM YOUR FIRST IMPRESSION

Horowitz describes growing up across social groups with different perspectives. These experiences shaped his habit of questioning initial interpretations.

Application: write down what you observed, then list plausible explanations. Ask someone close to the work what you are missing.

A convincing story becomes more useful when its assumptions are visible and testable.

YOUR DECISIONS AFFECT PEOPLE OUTSIDE WORK

Early in his career, Horowitz realized that his work choices were putting strain on his family. He changed jobs to address the situation.

The lesson is to make priorities explicit. A business plan consumes attention, health and family time as well as cash.

Discuss commitments with the people affected and revisit them when the company’s demands change.

FOUR QUESTIONS FOR A HARD DECISION

1. What specific outcome must we protect?
2. What facts and constraints shape the decision?
3. Which options remain and who bears each cost?
4. What evidence would make us revise the choice?

Write the answers before seeking agreement. This makes the disagreement concrete and gives the team a record it can learn from later.

THE LOUDCLOUD TO OPSWARE JOURNEY

1999: AN AMBITIOUS INFRASTRUCTURE BUSINESS

Loudcloud aimed to operate internet infrastructure for other companies. It raised substantial funding and expanded rapidly during the dot-com boom.

The model involved people, equipment and ongoing operating commitments. When demand and financing conditions deteriorated, those commitments became difficult to support.

Fast growth had created financial exposure.

2001: GOING PUBLIC UNDER PRESSURE

Loudcloud completed its IPO during the technology downturn. Horowitz describes it as a survival move made while the company’s financial outlook was weakening.

Public financing brought new expectations: quarterly results, forecasts and investor scrutiny.

Getting through one financing event left the underlying questions of demand, costs and cash generation unresolved.

THE HIDDEN ASSET INSIDE THE BUSINESS

Loudcloud had built Opsware software to automate infrastructure operations. Horowitz began exploring whether that internal capability could become an independent product.

A small team worked to separate it from Loudcloud’s environment.

The opportunity required real engineering: software that works inside one company may need substantial changes before outside customers can use it.

2002: THE BUSINESS MODEL CHANGES

EDS acquired Loudcloud’s managed hosting business on August 16, 2002 for $63.5 million in cash.

EDS also agreed to license Opsware software for $52 million over three years.

Loudcloud retained the software business and became Opsware. These figures come from EDS’s SEC filing, which resolves the inconsistent annual licence figures in the supplied transcript.

A PIVOT CREATES A NEW COMPANY TO BUILD

The shift changed the product, customers, revenue model and required executive skills. People who had performed well in the services business did not automatically fit the software business.

Horowitz had to explain the new opportunity, ship a usable product and rebuild leadership capability.

A pivot needs an operating transition, including clear roles and customer commitments.

2007: HP ACQUIRES OPSWARE

HP’s July 2007 announcement valued the transaction at approximately $1.6 billion, or $14.25 per share. The acquisition was completed in September.

HP’s annual report recorded an aggregate purchase price of approximately $1.7 billion, including additional accounting components.

The announced deal value and recorded purchase price use different measures.

WHAT THIS SUCCESS STORY CAN ESTABLISH

The transaction records establish that the transformation and acquisition happened. Horowitz’s account explains how he understood the decisions.

The outcome cannot prove that every tactic caused success or will work elsewhere. The story includes access to capital, relationships, timing and luck.

Use the cases to generate questions and options for your own circumstances.

MANAGING YOURSELF THROUGH THE STRUGGLE

"THERE IS ALWAYS A MOVE."

WHAT HOROWITZ MEANS BY THE STRUGGLE

The struggle describes the emotional pressure of building a company when expectations collapse: self-doubt, isolation and uncertainty about the next move.

Horowitz encourages founders to involve others and keep searching for workable options.

His language is motivational and autobiographical. Experiencing distress does not tell you whether a strategy is commercially viable.

SHARE THE PROBLEM WITH PEOPLE WHO CAN HELP

A founder may hide difficulties to protect the team’s confidence. That can prevent the people closest to the work from contributing solutions.

Share the relevant facts, explain the stakes and invite help. Protect personal and confidential information where appropriate.

Ask for specific contributions: a technical diagnosis, customer evidence, a cost estimate or a workable alternative.

CONVERT ANXIETY INTO A DECISION LIST

Create three lists:

1. Facts we can verify today.
2. Decisions we can make this week.
3. Uncertainties that require evidence.

Assign an owner and next action to each urgent item. Use a trusted adviser to challenge your reasoning.

The list creates a practical route from a vague sense of danger to work the team can complete and review.

KEEP PERSISTENCE CONNECTED TO EVIDENCE

Continuing makes sense when there is a credible path and enough resources to test it. Set review dates and conditions for changing direction.

Ask whether customers are receiving value, whether the economics can improve and what the next test will establish.

A responsible decision may involve continuing, narrowing scope, selling or closing. Personal worth does not depend on that choice.

TELL THE TRUTH AND MAKE IT SAFE TO SPEAK

OPTIMISM NEEDS CONTACT WITH REALITY

Horowitz describes becoming more effective after he stopped presenting an excessively positive picture. Employees could already see the problems.

When the CEO acknowledged those problems, the organization could work on them together.

A credible message explains what is happening, what remains uncertain and what the team will do next. Confidence grows through visible follow-through.

THREE REASONS TO SHARE BAD NEWS

1. Trust: people can compare leadership’s words with what they experience.

2. Problem-solving: employees need relevant information to contribute useful ideas.

3. Early warning: surfacing difficulties gives the company more time to respond.

A reporting culture depends on how managers behave when someone brings inconvenient information.

ALLOW PROBLEMS WITHOUT READY-MADE SOLUTIONS

An employee may identify a serious problem beyond their authority or expertise. Requiring a solution before they speak can leave the problem hidden.

Welcome the signal first. Clarify the evidence and urgency, then identify who can investigate it.

You can encourage initiative while also giving people a reliable way to escalate issues they cannot solve alone.

RESEARCH ADDS A USEFUL MECHANISM

Amy Edmondson’s 1999 study examined 51 work teams in one manufacturing company. Team psychological safety was associated with learning behavior.

It concerns whether people feel able to take interpersonal risks, such as admitting an error or asking for help.

This supports a mechanism for candid teamwork. The study does not establish that candor alone guarantees startup success.

"UNCERTAINTY AND INTERDEPENDENCE ARE ATTRIBUTES OF MOST WORK TODAY."

MAKE CANDOR A DAILY MANAGEMENT HABIT

Ask what the team is seeing that you might have missed. Acknowledge uncertainty and invite questions during real work.

When someone identifies an error, examine what happened and what should change. Close the loop by showing what their input affected.

Edmondson’s emphasis on inviting voices provides a useful safeguard when a founder feels pressure to control every decision.

A CLEAR CRISIS UPDATE

Use five short blocks:

1. Situation: what changed.
2. Evidence: what we know and do not know.
3. Impact: who and what are affected.
4. Action: priorities, owners and decisions.
5. Follow-up: when the next update will come.

Provide a channel for questions. If a decision is still pending, say when you expect to resolve it and who is accountable.

PROTECT SURVIVAL AND CREATE OPTIONS

UNDERSTAND THE FAILURE MECHANISM

Loudcloud’s difficulties involved declining customer demand, financing pressure and substantial operating commitments. Losing a large customer made the position worse.

The lesson is to identify how risks interact. A revenue loss can weaken customer confidence, slow new sales and intensify cash pressure.

Intervene at a point that materially changes this sequence.

REVENUE CONCENTRATION CAN SHAPE YOUR FUTURE

Horowitz reports that EDS represented about 90% of Opsware’s revenue during a critical account crisis. Its decision could determine whether the company survived.

For your business, examine dependence on the largest customers, channels and suppliers.

Ask what would happen if a major relationship ended and how long replacement revenue or capacity would take to secure.

BUILD A CASH VIEW THAT SUPPORTS DECISIONS

Prepare a rolling weekly view of expected cash receipts and payments. Include committed costs, uncertain collections and the timing of major decisions.

Run a downside scenario in which an important deal is delayed or lost.

Use the result to identify the latest date for action. A forecast is a model to update as evidence changes; it cannot remove uncertainty.

CREATE OPTIONS BEFORE THE DEADLINE

Work on separating Opsware began before Loudcloud sold its hosting business. That preparation created an option when circumstances worsened.

Look for capabilities, customer segments or partnerships that could support a viable alternative.

Estimate the cost and time to make each option real. An idea that cannot be implemented within available resources offers limited protection.

IDENTIFY WHO CAN ACTUALLY MAKE THE DEAL

In the EDS negotiations, Horowitz and John O’Farrell examined the organization to find a person who understood the strategic need and could influence a purchase.

Application: map the buyer, users, sponsor, budget owner and final approver.

Learn what each needs to evaluate the proposal. A promising conversation creates value when it leads to a workable decision process.

MAKE COMMITMENTS DELIBERATELY

For any major deal, specify the scope, dependencies, decision process and credible timeline. Understand what your company must deliver after signing.

Document the downside if assumptions fail and identify the people affected.

Negotiation success includes an agreement the business can execute. A signed contract can create new obligations as well as immediate relief.

RECOVER A CRITICAL CUSTOMER

THE EDS ACCOUNT CRISIS

Opsware’s deployment at EDS encountered technical and operational difficulties. Horowitz recounts a 60-day window to improve the situation.

The response combined intensive delivery work with a deeper understanding of what the customer valued.

Treat the timeline and conversations as the author’s account. They illustrate a recovery approach, rather than a tested universal formula.

RUN TWO CONNECTED RECOVERY TRACKS

Track 1: repair the promised outcome. Identify deployment failures, assign owners and remove obstacles.

Track 2: understand the customer’s wider priorities. Discover what the decision-maker values and what creates frustration.

Keep the tracks connected. Additional value is more credible when the team is also making visible progress on the original commitment.

REMOVE BLOCKERS ON A SHORT CYCLE

Horowitz held daily meetings with the team handling the account so unresolved obstacles could be escalated quickly.

Application: ask what is blocked, who can decide and when the decision is needed. Give the recovery owner access to the required people.

Keep the meeting focused on decisions. Track completed work and customer confirmation alongside internal activity.

TANGRAM REVEALED AN UNEXPECTED PRIORITY

The team learned that an important EDS decision-maker valued Tangram’s inventory software. Opsware arranged to acquire Tangram and include its software in the customer relationship.

Horowitz presents this as a turning point in restoring the account.

The transferable lesson is to understand the customer’s operating context. The acquisition itself was a highly specific response.

A RECOVERY PLAN THE CUSTOMER CAN EVALUATE

Agree on:

1. The outcome currently failing.
2. Evidence that will demonstrate recovery.
3. The owner on each side.
4. Milestones and dependencies.
5. Update frequency and escalation path.

At each review, show what changed and ask the customer to confirm whether it resolves the problem. Record any remaining disagreement before making further commitments.

KNOW THE LIMITS OF A RESCUE

Before approving exceptional recovery work, estimate delivery cost, opportunity cost and the effect on other customers.

Ask whether the solution is reusable and whether the future relationship can become sustainable.

A major customer deserves serious attention. The recovery plan also needs a clear boundary, a review date and a realistic account of what the company can promise.

IMPROVE THE PRODUCT AND KNOW WHEN TO PIVOT

"THERE ARE NO SILVER BULLETS FOR THIS, ONLY LEAD BULLETS."

WHAT THE LEAD BULLETS METAPHOR MEANS

Horowitz uses lead bullets to describe sustained work on a concrete competitive weakness. At Netscape and later Opsware, product improvements were essential to winning customers.

The lesson begins with diagnosis. Understand why customers choose another option, then improve the capability that affects their decision.

A new initiative needs a credible link to that problem.

FIND THE REASON CUSTOMERS CHOOSE ELSEWHERE

Review recent losses and ask customers:

1. What outcome were you trying to achieve?
2. Which requirement mattered most?
3. Where did our offer fall short?
4. What evidence influenced your choice?

Compare answers across accounts. Distinguish issues involving product performance, implementation, price, trust and buying process before deciding what to change.

CHOOSE THE TYPE OF CHANGE REQUIRED

Consider targeted improvement when customers value the category and the weakness can be repaired within available resources.

Consider a pivot when the customer, economics or delivery model requires a more fundamental change.

Define what evidence supports the choice. Set a review date and an observable result so persistence does not become an unexamined default.

INTERNAL SOFTWARE NEEDS EXTERNAL LEARNING

Opsware initially reflected Loudcloud’s own environment and requirements. Horowitz pushed the company to engage outside customers so the team could discover broader needs.

Application: test with a clearly defined user group and a bounded scope. Observe setup, usage and failure points.

Use what customers actually do to revise priorities and clarify the product’s limitations.

TURN A WEAKNESS INTO AN IMPROVEMENT CYCLE

1. Select a customer problem with clear evidence.
2. Record the baseline.
3. Assign a delivery owner.
4. Ship a focused improvement.
5. Validate the result with users.
6. Decide whether to continue, revise or stop.

Measure the outcome that matters to the customer, such as task completion, reliability or setup time. Keep the cycle small enough to learn quickly.

EXAMPLE: REPEATEDLY REJECTED CREATIVE WORK

A design agency keeps losing renewals because clients request repeated revisions.

The founder reviews rejected work and discovers inconsistent briefs. The team introduces a brief checklist, an early concept review and explicit acceptance criteria.

It then tracks revision rounds and on-time acceptance. The next decision follows the results of this test, including client feedback.

DEFINE THE PRODUCT MANAGER’S RESPONSIBILITY

Horowitz’s training document emphasizes customer knowledge, clear priorities, written decisions and responsibility for product outcomes.

His CEO-of-the-product metaphor expresses ownership. Formal authority depends on the organization.

Make the role concrete: identify the user, define the problem and coordinate decisions with engineering, design, sales and leadership.

MAKE PRODUCT KNOWLEDGE REUSABLE

Capture the customer problem, intended outcome, priorities and unresolved choices in a short written brief. Create answers to recurring sales and support questions.

Review the material when the product changes. Assign an owner for keeping it accurate.

A shared reference reduces repeated explanations and lets teams challenge the same assumptions before they make commitments.

BUILD A GOOD WORKPLACE THROUGH DAILY MANAGEMENT

"WE TAKE CARE OF THE PEOPLE, THE PRODUCTS AND THE PROFITS, IN THAT ORDER."

THE MEANING BEHIND THE PRIORITY ORDER

Horowitz attributes the previous quotation to his former boss Jim Barksdale. He connects it to the quality of employees’ working lives.

People need clear expectations, useful support and a fair chance to contribute. Those conditions help the company deliver its product.

The saying is a management priority, with financial viability still an essential operating constraint.

A GOOD WORKPLACE MAKES USEFUL WORK POSSIBLE

Horowitz describes a good company as a place where people understand their work and can expect their contribution to matter. Confusing responsibilities and ignored problems undermine that experience.

Assess the work directly: can employees get decisions, obtain help and understand how success is judged?

Use their answers to identify a management practice that needs attention.

TRAINING MAKES EXPECTATIONS USABLE

Horowitz argues that training helps people understand what good work requires and gives managers a foundation for feedback.

Start with essential job skills and practical expectations. Use examples from actual work and check whether employees can apply the material.

Training quality depends on relevance, practice and follow-up. Attendance alone does not establish competence.

TEACH BOTH THE JOB AND THE MANAGEMENT ROLE

Functional training covers the product, tools, standards and decisions needed in a particular job.

Management training covers setting objectives, giving feedback, developing people and conducting useful conversations.

Horowitz recommends involving managers and internal experts. The CEO should make leadership expectations explicit and support the time needed to teach them.

CHECK THE FULL COST OF A TRAINING INVESTMENT

Illustration: ten people each work 2,000 hours annually. A sustained 1% productivity improvement equals 200 hours of capacity.

Four hours of classes cost 40 learner-hours. Add 12 preparation hours and four teaching hours: 56 hours invested.

Potential net gain: 144 hours before other costs. The 1% gain is an assumption to test; saved capacity is not automatically cash.

START WITH ONE TASK PEOPLE REPEATEDLY GET WRONG

Choose a frequent task with costly mistakes. Show a completed example, explain the standard and let the employee practice on realistic work.

Review the result together and clarify the recurring errors. Keep the instructions short enough to use during the task.

Measure readiness through demonstrated performance and the support required after training.

GIVE ONE-ON-ONES A CLEAR PURPOSE

A one-on-one gives employees room to raise concerns, unfinished ideas, working relationships and development needs. Horowitz recommends that the employee shape the agenda and the manager listen closely.

Keep routine status reporting brief. Ask about issues that other channels miss and agree on follow-up.

A fixed speaking-time ratio is a coaching heuristic, not a validated requirement.

QUESTIONS THAT REVEAL THE WORKING EXPERIENCE

Ask:

1. Where are you waiting for a decision?
2. What expectation feels unclear?
3. Which recurring task needs a better method?
4. What would help you develop?
5. What issue have we discussed without resolving?

Close with the action each person will take. Revisit those commitments at the next meeting so raising an issue leads to a visible response.

INSPECT MANAGEMENT ACROSS THE EMPLOYEE JOURNEY

Examine recruiting, compensation, onboarding, feedback, development and departures.

HR can help identify weak processes and patterns across teams. Managers remain responsible for the daily experience they create.

Look for evidence such as unclear expectations, slow onboarding and unresolved concerns. Use the findings to improve management and check whether the change helped.

HIRE AND INTEGRATE THE RIGHT EXECUTIVES

HIRE FOR THE WORK THE COMPANY ACTUALLY HAS

A senior title or large-company track record does not establish fit for a smaller company’s immediate needs. Horowitz emphasizes the work required over the next stage.

Define the outcomes, resources and constraints of the role. Test the strengths required to deliver them.

Consider how the candidate works when the supporting systems of their previous company are unavailable.

THE MARK CRANNEY HIRING CASE

After several unsuccessful sales-leadership hires, Horowitz temporarily ran sales himself. This clarified what Opsware needed.

Mark Cranney demonstrated detailed knowledge of selling, recruiting and training. Horowitz hired him despite concerns about his presentation and fit.

The useful lesson is to examine evidence of essential capability and identify behavior that needs management.

LEARN ENOUGH TO DEFINE THE ROLE

Study the function before selecting its leader. Speak with capable practitioners and examine real work. Where feasible, take temporary responsibility for parts of the role.

Write down the expected early outcomes and critical strengths.

Domain experts can help assess skill. The hiring decision also needs knowledge of the company’s stage, constraints and working relationships.

BUILD AN INTERVIEW AROUND EVIDENCE

1. Define the required strengths and acceptable gaps.
2. Design questions that test those strengths.
3. Assign interviewers to areas they can evaluate.
4. Examine specific work and decisions.
5. Check references against the same criteria.

Bring the findings together before deciding. Record unresolved concerns and how the integration plan will address them.

CHECK THE SHIFT FROM LARGE COMPANY TO STARTUP

A leader moving from an established business may face a different working rhythm and skill requirement. The startup needs someone who can initiate work and build missing systems.

Ask what they would do in the first month, which resources they previously relied on and what they expect to change.

Evaluate their ability to adapt using concrete examples.

ONBOARDING STARTS WITH REAL WORK

Agree on early deliverables while the executive learns the product, customers and team. Identify the people they must meet and decisions they need to understand.

Provide frequent feedback and remove unclear dependencies.

Assess learning and contribution against the role’s actual complexity. A universal 30-day dismissal rule would ignore differences in context and support.

"2% OF ZERO IS ZERO."

LOOK FOR AMBITION THAT SUPPORTS SHARED SUCCESS

Horowitz recalls Cranney’s previous saying while discussing ambition for company success. Ask candidates how they shared credit, resolved competing priorities and helped colleagues succeed.

Confirm examples with people who worked with them.

Pronoun choices are weak evidence by themselves. Interest in fair compensation or career development is compatible with strong teamwork.

CHOOSE THE KNOWLEDGE THE ROLE REQUIRES

Identify which knowledge would be hardest to acquire in time: the company’s systems and relationships, or experience the team currently lacks.

Compare an internal candidate’s development needs with an external candidate’s integration needs.

Make the choice specific to the role. Age, previous title and company prestige do not establish the answer.

PROTECT TRUST DURING SENSITIVE RECRUITING

Hiring from a partner’s or friend’s company can create competing interests. Recognize the relationship early and keep the candidate informed about your process.

Protect the candidate’s confidentiality and obtain permission before contacting a current employer.

Assess the person on the role’s criteria. Keep their career choice and the business relationship in view.

USE FOUR DIMENSIONS TO REVIEW EXECUTIVES

1. Results: progress against agreed objectives.
2. Management: the team’s capability and working experience.
3. Innovation: investment in future effectiveness.
4. Peer relationships: coordination across leadership.

Review both achievements and how they were produced. This helps expose results obtained by exhausting the team or creating problems for another function.

HANDLE DIFFICULT PEOPLE DECISIONS WITH RESPECT

LAYOFFS CHANGE THE RELATIONSHIP OF TRUST

When a company reduces staff because its plan failed, employees need a clear account of what happened. Horowitz emphasizes leadership responsibility and respect for the people affected.

Those who remain will observe how colleagues are treated.

The operating task includes careful preparation, direct communication and a credible explanation of how the smaller company will function.

SIX ELEMENTS OF HOROWITZ’S LAYOFF APPROACH

1. Prepare yourself to lead the decision.
2. Avoid unnecessary delay once prepared.
3. Explain the business reason clearly.
4. Prepare managers for the conversations.
5. Give the company appropriate context.
6. Remain available afterward.

These are management principles. The actual process must account for local requirements, contracts and the circumstances of affected employees.

PREPARE THE HUMAN DETAILS

Before communicating a workforce change, establish who will speak with each person, what information is available and where questions will go.

Prepare accurate details about the transition and available support. Coordinate timing with the people responsible for the process.

A difficult conversation needs clarity, privacy and space for the employee to respond.

"YOU ABSOLUTELY CAN LET HIM KEEP HIS RESPECT."

THE CONTEXT BEHIND CAMPBELL’S ADVICE

Horowitz attributes the previous quotation to Bill Campbell during preparation for an executive dismissal.

The principle is to protect the person’s dignity while clearly communicating the decision. Avoid public blame and unnecessary disclosure.

The wording is a reported recollection in the supplied source, rather than an independently recorded statement from Campbell.

STUDY THE SYSTEM BEHIND AN EXECUTIVE MISMATCH

Review the conditions that produced the mismatch:

1. Was the role defined clearly?
2. Did hiring test the essential strengths?
3. Did the company need this experience now?
4. Was the person integrated effectively?
5. Did the business change?

The review should improve future decisions. Replacing a person without learning from the process can reproduce the same problem.

WHEN A LOYAL COLLEAGUE’S ROLE MUST CHANGE

A business may outgrow the role originally given to a trusted colleague. Prepare for the person to feel embarrassment or betrayal.

Explain the future requirements, acknowledge their contribution and discuss a meaningful alternative if one exists.

Do not assume they will stay. The transition needs a plan that respects their choice and protects continuity for the team.

KEEP WORK MOVING THROUGH A LEADERSHIP CHANGE

Before announcing a departure, identify who will make decisions, manage direct reports and own current commitments.

Communicate promptly with the people most affected and give them a clear reporting arrangement. Preserve the departing person’s dignity.

If the CEO temporarily takes the role, the operational responsibilities still need attention: meetings, feedback, priorities and follow-up.

DESIGN INCENTIVES AND PAY DOWN MANAGEMENT DEBT

METRICS INFLUENCE WHAT PEOPLE DO

A team pays attention to what leaders measure, discuss and reward. If those signals cover only part of the real objective, employees can hit the target while missing the intended outcome.

Before setting a metric, ask what behavior it encourages and what important quality it leaves invisible.

Review results alongside customer experience and the work that produced them.

THE SALES-TIMING INCENTIVE BACKFIRED

To reduce the concentration of deals at quarter-end, Horowitz offered bonuses for earlier closes. He reports that some deals moved into the early months of the following quarter.

The pattern became smoother while the quarter became smaller.

The case illustrates a priority conflict. A leader must decide what trade-off is acceptable before introducing the incentive.

A PRODUCT CAN PASS EVERY INCOMPLETE TEST

Horowitz describes a team delivering the planned features on schedule with few bugs, yet producing a mediocre product. The measures had omitted whether the features mattered to customers.

Application: inspect user outcomes alongside delivery and quality measures.

A completed feature is evidence of output. Its value requires observation of what the customer can accomplish.

ADD GUARDRAILS TO THE MAIN TARGET

For each target, define:

1. The intended customer or business outcome.
2. The behavior it should encourage.
3. A plausible way it could be gamed.
4. A quality or sustainability guardrail.
5. A review using quantitative and qualitative evidence.

Example: measure support resolution time alongside reopened cases and confirmation that the customer’s issue was resolved.

WHAT MANAGEMENT DEBT MEANS

Management debt is the future cost created by an expedient organizational decision. A shortcut may buy time while creating confusion or incentives that become expensive later.

Horowitz’s examples include unclear shared leadership, inconsistent compensation and missing feedback.

The metaphor prompts a useful question: what future work are we creating with today’s decision?

SHARED LEADERSHIP NEEDS CLEAR DECISION RIGHTS

Putting two people in charge of the same function can leave employees unsure whose decision stands and who owns the result.

If responsibilities are shared, specify the decisions each person owns, how conflicts are resolved and who is accountable for the overall outcome.

Check whether the arrangement works in practice. Repeated escalation is evidence that the design needs attention.

COMPENSATION EXCEPTIONS CREATE PRECEDENTS

A retention offer may protect an urgent project while changing expectations about how pay decisions are made. Evaluate the employee’s role, contribution and the consistency of the decision.

Investigate genuine underpayment and review comparable cases.

Document why an exception is justified and what wider adjustment may be needed. Legitimate pay concerns deserve examination.

MISSING FEEDBACK CREATES DELAYED PROBLEMS

When expectations and feedback remain informal, people may discover serious performance concerns only after frustration has accumulated.

Clarify the expected work early. Discuss examples, give timely feedback and agree on support.

A lightweight review process can create continuity. The useful output is shared understanding of performance and the next improvement to make.

KEEP A MANAGEMENT DEBT REGISTER

Record each temporary compromise:

1. The decision and reason.
2. The benefit gained now.
3. The future cost or risk.
4. The person responsible for resolving it.
5. The date or trigger for review.

Prioritize debt that repeatedly blocks work, damages trust or makes accountability unclear. Close an item only when the underlying issue has been resolved.

MAKE PROMOTIONS AND ORGANIZATIONAL DECISIONS FAIR

UNDERSTAND THE INCENTIVES BEHIND POLITICS

Horowitz uses politics to mean advancing an agenda through means disconnected from merit and contribution. He argues that leaders can encourage this unintentionally.

Private promises, inconsistent exceptions and ambiguous authority create opportunities for maneuvering.

Make decisions through clear criteria and distinguish an exploratory discussion from an actual commitment.

CREATE A CONSISTENT REVIEW PROCESS

Use clear criteria for performance, compensation and promotion. Gather comparable evidence and explain the timing and decision process.

Provide a route to raise errors or missing information. Evaluate exceptions explicitly.

Consistency makes decisions easier to assess. It also helps quieter employees whose contribution might otherwise receive less attention.

HANDLE COMPLAINTS WITHOUT TURNING RUMOR INTO FACT

Listen to the specific claim, gather evidence and give appropriate people a fair chance to respond. Clarify what remains unverified.

A facilitated conversation may help an ordinary working disagreement. Sensitive allegations need an appropriate confidential process.

Avoid assuming that every complaint is politics or requiring a joint confrontation in every situation.

TITLES COMMUNICATE SCOPE AND INFLUENCE

Titles help employees, customers and partners understand responsibilities. They also become reference points for recognition and compensation.

Define the skills, scope and decisions attached to each level. Review comparable roles across teams.

A title should provide useful information about the job and fit within an understandable internal system.

TWO HISTORICAL APPROACHES TO TITLE SIZE

Horowitz describes Andreessen as favoring generous titles as a recruiting tool and Zuckerberg as favoring restrained titles to reinforce internal levels.

Each approach carries trade-offs involving attraction, consistency and clarity. These are historical descriptions.

Choose a policy that fits the company, then apply explicit standards for actual responsibility and advancement.

PROMOTION REQUIRES EVIDENCE FOR THE NEXT ROLE

The Peter Principle describes a risk of promoting people based on success in a previous role until they reach work they cannot perform effectively.

Treat it as a warning about changing job requirements.

Define the next role’s skills and look for evidence of readiness. Support development and consider expert career paths that do not require managing a team.

RESEARCH SUPPORTS CHECKING MANAGERIAL CAPABILITY

Benson, Li and Shue studied sales workers at 214 firms. Their findings were consistent with firms emphasizing current sales performance in promotions over other signals that better predicted managerial performance.

This supports examining the skills the new role needs.

The evidence comes from sales organizations and does not imply that every top performer will be a poor manager.

PREVENT WEAK PRECEDENTS FROM SETTING THE STANDARD

Horowitz warns that employees may compare themselves with the weakest person at the next title level. One inconsistent promotion can become an argument for more.

Use documented role standards and evidence from the candidate’s work. Calibrate decisions across teams and address existing mismatches.

His named law is a provocative heuristic, rather than a scientific law.

MAKE CULTURE VISIBLE IN EVERYDAY BEHAVIOR

CHOOSE THE WORKING PRACTICES YOU WANT TO PRESERVE

In this discussion, Horowitz defines culture through ways of working that support the mission and endure as the company grows.

Much of it emerges from the behavior of founders and early employees. Deliberately choose a few operating values and connect them to repeated actions.

Assess whether those actions help people deliver the intended customer and business outcomes.

HISTORICAL CULTURE MECHANISMS

Horowitz discusses Amazon’s door desks as a signal of frugality and a16z’s lateness fine as a signal of respect for entrepreneurs’ time.

The examples show how a visible practice can prompt a conversation about priorities.

They are historical illustrations. Select mechanisms suited to your own work and check their effects on people and performance.

TRANSLATE A VALUE INTO A REPEATABLE ACTION

Example value: make client commitments reliable.

Practice: before promising a delivery date, record the scope, responsible owner and acceptance criteria.

Reinforcement: review missed commitments to find planning and handoff problems.

The value becomes visible through a decision people repeat. Check whether the practice improves reliability without adding unnecessary delay.

EXPLAIN THE BOUNDARIES OF ACCEPTABLE CONDUCT

Horowitz’s profanity example illustrates the importance of explaining a policy and its boundaries. It does not establish that harsh language is necessary for strong performance.

Define expected conduct in terms people can apply. Leaders should follow the same expectations and respond to concerns.

The absence of complaints alone cannot establish that everyone feels comfortable.

EVALUATE TALENT THROUGH ITS EFFECT ON THE TEAM

A capable employee can make collaboration difficult through repeated unreliability, intimidation or destructive interactions.

Assess observable behavior and its effect on work. Clarify expectations and examine whether management failures are contributing.

Preserve room for disagreement and different working styles. Avoid using personality labels or assumed medical causes as an assessment.

KEEP CHALLENGE PRODUCTIVE AND INFORMATION ACCESSIBLE

Investigate the substance of criticism even when its delivery is uncomfortable. Check whether employees have an effective route to raise problems.

At the same time, address conduct that repeatedly shuts others out of discussion.

A team needs both access to difficult information and workable relationships. Use specific examples to explain what must change and why.

USE BOLD CLAIMS WITH THEIR LIMITS ATTACHED

Part 2 includes sweeping claims about tenfold product advantages, hiring patterns and company size. These reflect Horowitz’s views and historical setting.

A tenfold advantage is not a universal adoption threshold, and headcount does not establish a company’s importance.

Test the actual customer benefit, switching costs, economics and organizational needs of your business.

SCALE COMMUNICATION, ROLES AND PROCESSES

GROWTH CHANGES THE COORDINATION PROBLEM

As a team grows, shared knowledge becomes less complete and decisions involve more people. Adding staff can increase coordination work before it increases useful output.

Horowitz identifies specialization, organizational design and process as responses.

Introduce structure where communication or ownership is failing, then check whether it improves the flow of work.

SPECIALIZATION CREATES HANDOFFS TO MANAGE

Early employees may handle many stages of a task. Specialization allows deeper expertise, but work must then pass between people or teams.

Define what each specialist produces, what the next person needs and how exceptions are resolved.

Assess the complete customer outcome. A fast individual stage can still leave the overall process slow if the handoff is unclear.

DESIGN THE ORGANIZATION AROUND COMMUNICATION

1. List the knowledge people must share.
2. List recurring decisions.
3. Prioritize critical communication paths.
4. Choose leaders for the groups.
5. Identify the connections the structure weakens.
6. Add ways to support those connections.

Every structure has trade-offs. Explain the chosen priorities and review the design when the work changes.

"THE PURPOSE OF PROCESS IS COMMUNICATION."

GIVE EACH PROCESS AN OBSERVABLE OUTPUT

A process defines how information and work move reliably between people. Start with the intended output, then design the steps required to produce it.

Involve the people already doing the work. Specify responsibility, inputs and the signals that reveal a problem.

Keep the process proportionate to the coordination challenge and revise it when its assumptions change.

EXAMPLE: HIRING AS A COMPLETE PROCESS

The desired outcome is a productive colleague who fits the role. Review the full sequence:

Role definition → sourcing → assessment → offer → onboarding → contribution.

Check where candidates or new hires become stuck. Give each stage an owner and a useful completion criterion.

This makes it easier to identify whether the bottleneck is selection, acceptance, learning or management.

ADD STRUCTURE AT THE POINT IT BECOMES USEFUL

Adding a process too early can slow a small team. Waiting too long can leave a larger team dependent on repeated explanations and founder intervention.

Watch for recurring handoff failures, conflicting decisions and difficult onboarding.

Introduce the smallest useful change, explain its purpose and review whether the problem has become less frequent.

DEVELOP PEOPLE AS THE COMPANY GROWS

Horowitz cautions against assuming that a capable executive will fail at a future scale they have never experienced. Such a judgment can lead a leader to withhold development.

Evaluate current performance and the next concrete requirement. Provide support and assess learning.

Revisit the decision with new evidence as the role changes.

RECONCILE DEVELOPMENT WITH A NECESSARY ROLE CHANGE

Part 1 describes changing a loyal colleague’s role when requirements exceed their capability. Part 2 warns against deciding that someone cannot grow based on speculation.

Together, the practical question is whether the person can meet the actual requirements with appropriate support in the available time.

Make that assessment explicit and explain the evidence behind it.

MATCH LEADERSHIP TO THE SITUATION

PEACETIME IN HOROWITZ’S FRAMEWORK

Horowitz describes peacetime as a period with a strong competitive position in a growing market. Leadership can invest in expansion, creativity and organizational development.

His examples reflect the technology industry when the essay was written in 2011.

Use the concept as a way to examine conditions. It is a management metaphor with boundaries that require judgment.

WARTIME IN HOROWITZ’S FRAMEWORK

Wartime describes an imminent threat to the company’s survival. Horowitz argues for concentrated priorities, decisive leadership and close attention to the critical mission.

The practical questions are what threatens survival, which actions address it and who must decide.

A company can face different conditions across teams, products and time periods.

KEEP INFORMATION FLOWING UNDER PRESSURE

Centralizing an urgent decision can help coordination. It can also make a founder harder to challenge.

Preserve a way for specialists to report errors, risks and contrary evidence. Clearly separate who supplies information from who owns the decision.

This combines Horowitz’s emphasis on focus with research on speaking up. The combined approach is an application, not a proven formula.

DEFINE THE BOUNDARIES OF CRISIS MODE

Record:

1. The threat and evidence.
2. The small set of urgent priorities.
3. Temporary changes to decision authority.
4. How people can raise concerns.
5. A review date and exit conditions.

Check whether concentrated attention is still needed. Prolonged emergency behavior can make ordinary planning, learning and delegation difficult.

RECOGNIZE SELF-DECEPTION AND LEARN FROM EVIDENCE

WATCH FOR CONVENIENT EXPLANATIONS

Under pressure, a team may explain away lost customers, missed milestones or employee departures. The explanation can feel reasonable while leaving the underlying issue untouched.

Horowitz describes this as people deceiving themselves.

Ask what evidence supports the explanation, what contradicts it and what you would expect to observe if another explanation were correct.

FOUR CLAIMS WORTH INVESTIGATING

1. A strong employee left, but the team says the departure is harmless.
2. A lost deal is attributed entirely to price.
3. Missed milestones are assumed to have no effect on delivery.
4. High churn is expected to disappear after more marketing.

Each explanation may contain truth. Verify it through records, customer conversations and the people closest to the work.

USE THE SAME STANDARD FOR GOOD AND BAD NEWS

Horowitz recalls Andy Grove observing that leaders may react enthusiastically to positive signals while finding excuses for negative ones.

Use consistent questions for both:

Is the measurement reliable? Is the change persistent? What else could explain it? What evidence should we gather next?

This gives encouraging and troubling signals a comparable level of scrutiny.

BUILD A DECISION LOG

For a consequential choice, record:

1. The decision and owner.
2. Facts available at the time.
3. Assumptions and uncertainties.
4. Alternatives considered.
5. Expected results and review date.

At review, compare expectations with outcomes. Identify what you learned about the customer, market or execution process and update the next decision accordingly.

UNDERSTAND WHAT THE EVIDENCE CAN SUPPORT

The deck combines corporate records, founder recollections and selected research. Each supports a different type of claim.

Author essays confirm Horowitz’s published views but are not independent tests of his methods. Team and promotion studies provide evidence within their settings.

Original applications translate the ideas into practice. Their suitability must be evaluated in your company.

TURN THE LESSONS INTO A WORKFLOW

STEP 1: STATE THE MOST IMPORTANT PROBLEM

Write one sentence describing the problem and its consequence.

Example: Clients are delaying approval because our delivered work repeatedly misses the agreed brief.

Attach the available evidence. List what remains uncertain and name the person responsible for resolving it.

Deliverable: a short problem statement that the team can discuss without guessing what it means.

STEP 2: DIAGNOSE THE CONSTRAINT

Review relevant work, speak with affected customers and ask the team where progress breaks down.

Separate symptoms from plausible causes. Identify the constraint that the next action can realistically change.

Deliverable: a diagnosis with evidence, open questions and the cost of waiting. If the cause remains uncertain, define a small test to distinguish the leading explanations.

STEP 3: CHOOSE A TESTABLE RESPONSE

Compare feasible responses by expected benefit, resources, risk and time to learn. Choose a focused action with an owner and a measurable result.

Add a quality guardrail and check the behavior the target may encourage. Identify required training or decision authority.

Deliverable: an execution decision with a review date and clear conditions for continuing or revising it.

STEP 4: ALIGN THE PEOPLE DOING THE WORK

Explain the situation, the chosen response and each person’s responsibility. Make dependencies visible and provide a route for questions or blockers.

Check that people understand what completion means. Confirm that the plan fits their actual capacity.

Deliverable: a shared work plan with owners, expected outputs and a simple schedule for updates.

STEP 5: EXECUTE AND REVIEW

Remove blockers, complete the agreed work and collect evidence of the result. Ask affected users whether the change helped.

Compare outcomes with the initial expectation. Decide what to continue, revise or stop.

Deliverable: a brief review with the next decision. Preserve the learning in a reusable playbook so the next team can start with better information.

STEP 6: MAKE THE IMPROVEMENT REPEATABLE

Capture the working method, owner, handoff and acceptance criteria. Teach it to the people who will use it.

Update a process, role expectation or incentive if the review exposed a recurring management issue. Add unresolved compromises to the management debt register.

Deliverable: a reusable playbook and the next review date. Check that the improvement survives beyond its first success.

YOUR FOUNDER REVIEW

Ask regularly:

1. What difficult fact needs attention?
2. Which customer outcome is failing?
3. What threatens continuity?
4. Who needs a decision or support?
5. What behavior are our targets rewarding?
6. Which management debt keeps recurring?
7. What did we learn?

Choose one issue. Assign an owner, expected deliverable and review date. Turn the result into a repeatable practice.

CREATE YOUR EXECUTION PLAN

Use this WorkFlow prompt:

My business is [type]. Our problem is [problem], supported by [facts]. We have [resources] and [deadline]. Create WorkSteps with owners, expertise, tools, deliverables and review points. Include training, handoffs and metric guardrails where relevant. Mark assumptions.

Customize the plan in AgentX.ID and start with the highest-priority action.

SOURCES AND VERIFICATION

S1: SUPPLIED SOURCE

The Hard Thing About Hard Things, Part 1. User-supplied audiobook transcript covering the early history and crisis-management lessons.

Video identified in the attachment:
https://www.youtube.com/watch?v=vqy1S9iF56c

Used for the author’s recollections and reported conversations. The transcript contains recognition errors; disputed transaction figures were checked separately.

S2: LOUDCLOUD SALE TO EDS

EDS 2004 Form 10-K, Note 16: acquisition completed August 16, 2002 for $63.5 million in cash; software licence of $52 million over three years.

https://www.sec.gov/Archives/edgar/data/1007456/000119312505059935/d10k.htm

This record supports the transaction details and corrects inconsistent licence amounts in S1.

S3: HP ANNOUNCES THE OPSWARE ACQUISITION

HP Form 8-K filed July 23, 2007: $14.25 per share and approximately $1.6 billion announced transaction value.

https://www.sec.gov/Archives/edgar/data/47217/000104746907005776/a2178943z8-k.htm

Used for the announced terms. The agreement date and final completion date are different events.

S4: HP RECORDS THE COMPLETED ACQUISITION

HP 2007 Form 10-K, Note 7, Opsware Acquisition: completion in September 2007 and approximately $1.7 billion aggregate purchase price including accounting components.

https://www.sec.gov/Archives/edgar/data/47217/000104746907010151/a2181429z10-k.htm

Used to distinguish the final recorded amount from the announcement figure.

S5 AND S6: FOUNDER PSYCHOLOGY AND LEADERSHIP

S5. The Struggle, June 15, 2012. Source of the quote: There is always a move.
https://a16z.com/the-struggle/

S6. Peacetime CEO/Wartime CEO, April 14, 2011. Defines the leadership metaphor.
https://a16z.com/peacetime-ceo-wartime-ceo/

Both are practitioner perspectives. Their historical examples and prescriptions require context.

S7 AND S8: PRODUCT WORK AND TRAINING

S7. Lead Bullets. Source of the quotation and the product-improvement cases.
https://a16z.com/lead-bullets/

S8. Why Startups Should Train Their People, May 14, 2010. Adds guidance on training and expectations.
https://a16z.com/why-startups-should-train-their-people/

These explain Horowitz’s reasoning; they do not independently test the effectiveness of each practice.

S9: PSYCHOLOGICAL SAFETY RESEARCH

Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383, 1999.

https://doi.org/10.2307/2666999

Study of 51 teams in one manufacturing company. Supports the association between team psychological safety and learning behavior. Generalization and causal interpretation require care.

S10: INVITING PEOPLE TO SPEAK UP

Four Steps to Building the Psychological Safety That High-Performing Teams Need. Kara Baskin, featuring Amy Edmondson, June 14, 2023. Source of Edmondson’s quote and practical leadership guidance.

https://www.library.hbs.edu/working-knowledge/four-steps-to-build-the-psychological-safety-that-high-performing-teams-need-today

S12 AND S13: MANAGEMENT DEBT AND SCALING

S12. Management Debt. Defines the metaphor and describes its organizational examples.
https://a16z.com/management-debt/

S13. Taking the Mystery out of Scaling a Company. Explains specialization, structure and process.
https://a16z.com/taking-the-mystery-out-of-scaling-a-company/

These corroborate the author’s published ideas. They are not independent empirical validation.

S14 AND S15: CONVERSATIONS AND TEAM EFFECTIVENESS

S14. One On One. Explains employee-led conversations and listening.
https://a16z.com/one-on-one/

S15. When Smart People are Bad Employees. Discusses how individual behavior affects the team.
https://a16z.com/when-smart-people-are-bad-employees/

The deck focuses on observable behavior and evidence. Anecdotal labels and assumed medical explanations are not used as assessment tools.

S16 AND S17: CULTURE AND PROMOTIONS

S16. Programming Your Culture, December 18, 2012. Explains practices intended to reinforce operating values.
https://a16z.com/programming-your-culture/

S17. Titles and Promotions, March 16, 2011. Discusses levels, promotion standards and historical title policies.
https://a16z.com/titles-and-promotions/

Examples retain their historical context.

S18: INDEPENDENT PROMOTION RESEARCH

Promotions and the Peter Principle. NBER Working Paper 24343, 2018.

https://www.nber.org/papers/w24343

Uses data on sales workers at 214 firms to examine promotion choices and managerial performance. Supports evaluating the requirements of the new role. The findings do not establish an inevitable outcome for every promotion or occupation.

KAIZEN

A repeated frustration is an opportunity to improve the way life or work happens.

Kaizen offers a practical method: observe the problem, test a change, study the result and preserve what helps.

This playbook explores its Japanese roots, essential tools, human principles and applications for individuals, teams and founders.

A GUIDE YOU CAN PUT TO WORK

Choose a task you repeat: preparing orders, publishing content, onboarding customers or studying.

As you read, identify its biggest source of friction. By the end, you will have a baseline, a small experiment, a review date and a way to sustain progress.

Examples and numerical scenarios are illustrative unless identified as documented research.

THE MEANING OF KAIZEN

WHAT THE JAPANESE WORD MEANS

Kaizen is written 改善.

改 conveys change or reform. 善 conveys goodness or a better condition. Together, they express improvement.

In management, Kaizen refers to continuing improvement involving people throughout an organization. The everyday Japanese word has a broader meaning than the management methods associated with it.

HOW THE PHILOSOPHY BECOMES PRACTICAL

A useful Kaizen mindset combines three commitments:

1. Notice difficulties in everyday work.
2. Involve the people who understand them.
3. Test and sustain better ways of working.

The practical question is: what change would make this process easier, safer or more valuable, and what evidence would show that it helped?

HOW SMALL GAINS ACCUMULATE

Illustration: a clearer template saves two minutes on a task performed 15 times a day.

That releases 30 minutes daily, or 10 hours across 20 working days.

The benefit lasts only if people use the template and it remains useful. Time released becomes financial value when it reduces spending or supports worthwhile additional work.

UNDERSTAND THE 1% ILLUSTRATION

The familiar calculation 1.01 to the power of 365 is approximately 37.8.

It assumes a measurable quantity grows by exactly 1% every day, with every gain retained and compounded.

Real progress includes plateaus, setbacks and limits. Use the calculation as an illustration of accumulation. It provides no forecast of personal or business performance.

JAPANESE ROOTS AND GLOBAL DEVELOPMENT

A MODERN MANAGEMENT TRADITION

Kaizen's management tradition grew through industrial learning, quality control and workplace experimentation.

Its history includes Japanese practitioners, international exchanges and institutions that helped spread methods across companies.

Describe it as a modern improvement philosophy rooted in Japanese management practice.

1950: QUALITY LEARNING ACCELERATES

The Union of Japanese Scientists and Engineers, known as JUSE, invited Deming in 1950.

His teaching contributed to Japan's development of statistical quality control and management thinking.

This is one important milestone in a broader history. Kaizen emerged through contributions from many people and organizations over time.

1962: QC CIRCLES BEGIN

JUSE dates the start of Japanese QC-circle activities to April 1962.

These small groups of frontline employees use quality methods to improve their work, products and services.

Their aims include developing members' abilities, improving the workplace and increasing customer satisfaction. Management provides guidance and support.

1986: MASAAKI IMAI EXPANDS GLOBAL AWARENESS

Masaaki Imai founded Kaizen Institute in 1985. His book Kaizen: The Key to Japan's Competitive Success followed in 1986.

He helped communicate Japanese improvement practices internationally. Gemba Kaizen, published in 1997, developed the workplace-focused approach further.

He was a major popularizer within a much longer history.

"THE STARTING POINT FOR IMPROVEMENT IS TO RECOGNIZE THE NEED."

TOYOTA GIVES THE PRACTICE A SYSTEM

Toyota describes daily Kaizen as part of the Toyota Production System, or TPS.

TPS combines jidoka, which detects abnormalities and stops defects from continuing, with just-in-time production matched to need.

Kaizen helps people refine how this system works. Toyota's account also emphasizes making work easier and developing people's capabilities.

THE FIVE CORE PRINCIPLES

1. KNOW YOUR CUSTOMER

Start by identifying who receives the outcome and what they value. Ask customers, observe their journey and distinguish real needs from internal assumptions.

Translate what you learn into a clear target.

Example: reduce order waiting time while preserving accuracy, product quality and a reasonable employee workload.

2. LET IT FLOW

Follow work from request to completed value. Look for queues, repeated approvals, unnecessary movement, rework and uneven handoffs.

Improve the whole journey instead of making one activity faster at another team's expense.

A useful change reduces friction while protecting quality, safety and sustainable workload.

3. GO TO GEMBA

Gemba means the actual place. Visit where the work occurs and observe the process directly with the people involved.

Watch an order being prepared, an invoice being checked or a user completing setup. Ask what makes the task difficult.

Data shows where a gap exists. Gemba helps reveal how and why it happens.

4. EMPOWER PEOPLE

The people closest to the work often see problems first. Invite their ideas, give them time to improve and define which safe experiments they may run.

Leaders remove obstacles, provide support and respond to suggestions.

Improvement grows stronger when employees help diagnose, test and sustain the change.

5. BE TRANSPARENT

Make the problem, target, experiment and result visible to everyone affected. Use shared definitions and simple measures so people can follow progress.

Report setbacks and unintended effects as clearly as gains.

After a useful test, document the new method, owner and review date so the improvement can be repeated and checked.

SEE THE PROBLEM CLEARLY

WRITE THE GAP IN OBSERVABLE TERMS

A useful problem statement describes an observable gap.

Illustration: during weekday lunch, 18 of 100 orders took longer than 10 minutes from payment to handover. Our target is no more than five.

This identifies a process, time period, measure and target. It leaves room to investigate causes before selecting a solution.

TRACE THE WHOLE JOURNEY

Map the steps from request to completed outcome. Record where information moves, work waits and responsibility changes.

Value-stream mapping formalizes this view of material and information flow.

A locally faster task may simply create a larger queue downstream. Judge the change by what happens to the complete customer journey.

MEASURE A CREDIBLE BASELINE

Define precisely when timing starts and stops, what counts as an error and which cases are included.

Collect observations across representative conditions. Record demand, staffing and unusual events.

Illustration: comparing a quiet Tuesday with a busy Saturday can make a layout change appear better or worse for unrelated reasons.

MUDA: RESOURCES USED WITHOUT CUSTOMER VALUE

Muda describes resource use that creates no customer value.

Some such work can be removed quickly. Other work remains necessary under current conditions until the underlying process changes.

Before removing a step, understand its purpose. A check may protect quality while the team develops a more reliable way to prevent errors.

THE SEVEN ORIGINAL WASTE CATEGORIES

1. Overproduction: making ahead of need.
2. Waiting: stalled work or people.
3. Transport: unnecessary transfers.
4. Overprocessing: unnecessary processing.
5. Inventory: excess stock.
6. Motion: unnecessary human movement.
7. Correction: defects, rework and scrap.

Use these categories to notice problems in the process you are observing.

THE EIGHTH WASTE IS A LATER EXTENSION

Many modern Lean descriptions add unused human talent to the original seven wastes.

It draws attention to ignored ideas and underused skills. Keep that distinction clear when explaining the history.

Practical example: a support employee repeatedly notices unclear wording, yet has no route to propose a product improvement.

MURA AND MURI EXPLAIN MORE OF THE SYSTEM

Mura means unevenness. Muri means overburden on people or equipment.

Illustration: a manager releases every approval at 4 p.m. The next team receives a sudden rush, works beyond reasonable capacity and makes errors.

Consider the release pattern, capacity and workload together. Removing visible waste alone may leave its causes unchanged.

PRIORITIZE WITH A PARETO CHART

A Pareto chart orders categories from largest to smallest. It helps identify where a problem is concentrated.

For example, classify order errors by type and count each category. Start investigating a frequent or costly category.

The familiar 80/20 relationship is a heuristic. Let the actual distribution guide the decision.

INVESTIGATE CAUSES WITH EVIDENCE

The Five Whys follows a chain of causes. A fishbone diagram organizes possible causes, such as methods, equipment and materials.

Both guide investigation. Check each proposed explanation against observations or tests.

A problem may have several interacting causes. Asking why five times does not establish that an explanation is true.

TEST A CHANGE AND LEARN

PDCA ORGANIZES THE IMPROVEMENT CYCLE

1. Plan: identify an opportunity and prepare a change.
2. Do: test it on a small scale.
3. Check: examine results and learning.
4. Act: use that learning to adapt or extend the change.

Repeat the cycle. A practical record should show what was tried, what happened and what the team decided next.

PDSA ADDS AN IMPORTANT LEARNING EMPHASIS

The Deming Institute explains that Deming emphasized PDSA, with Study as its third step.

Make a prediction before the test. Compare it with the outcome and revise your explanation of how the process works.

This distinction matters historically. Both cycles can support improvement when teams genuinely examine evidence and learn.

DESIGN A TEST YOU CAN INTERPRET

Suggested experiment card:

Change: move order labels beside the cup station.
Prediction: label-search time will fall.
Scope: one station for two comparable shifts.
Measure: search time per order and wrong-label rate.
Stop rule: pause if label errors increase.

Keeping the initial change focused makes its effect easier to investigate.

STUDY MORE THAN A SINGLE AVERAGE

Suppose the average gets faster while the longest waits become worse. Some customers may receive a poorer experience.

Review the distribution, repeated observations and relevant subgroups. Keep checking quality and workload.

A short pilot provides an early signal. Confidence grows when the benefit persists across comparable conditions.

DECIDE WHAT THE EVIDENCE SUPPORTS

Adopt a change when the evidence supports its benefit and safeguards hold. Adapt it when the result reveals a better test. Abandon it when it creates harm or lacks value.

Record the reasoning. An unsuccessful test can prevent a larger mistake.

Scale cautiously when the next team has different equipment, skills or demand.

HOLD THE GAIN

After a useful change, update the relevant instructions and show the people involved how to use them.

Assign responsibility for follow-up. Check the process after the initial attention has faded.

If performance slips, investigate what changed: the method may be unclear, materials unavailable or operating conditions different.

TOOLS THAT MAKE BETTER WORK EASIER

5S: ORGANIZE FOR RELIABLE WORK

1. Seiri: sort needed from unneeded items.
2. Seiton: arrange items for use.
3. Seiso: clean and inspect.
4. Seiketsu: standardize upkeep.
5. Shitsuke: sustain the habits.

Apply the sequence to physical or digital workspaces. Evaluate whether it makes needed items easier to find and problems easier to notice.

MAKE STATUS AND ACTION VISIBLE

Suggested small-team board:

Problem | Owner | Next test | Review date | Result

Keep it close to the work and update it during a brief review. An overdue test should prompt a decision about the obstacle.

For abnormalities, define who responds and what they do. Visibility becomes useful when people can act on the information.

DAILY KAIZEN AND FOCUSED WORKSHOPS

Daily Kaizen supports small, ongoing improvements within normal work. A focused Kaizen event brings a team together for concentrated analysis and change, often over several days.

A workshop can address a larger process redesign. It still needs ownership and follow-up.

Judge the format by sustained outcomes and the team's growing capability.

USE TOOLS SELECTIVELY

Need to locate delay? Map the process.

Need to prioritize error types? Use a Pareto chart.

Need to explore causes? Use a fishbone diagram and verify explanations.

Need to organize a workspace? Consider 5S.

For a simple problem, a short observation record and one controlled test may provide enough structure.

A COFFEE SHOP: THE COMPLETE CYCLE

THE CASE AND ITS BOUNDARIES

A takeaway coffee shop wants more reliable lunch service.

Over five comparable lunch periods, 18 of 100 measured orders exceeded 10 minutes from payment to handover.

The team sets a target of no more than five late orders per 100. It will also monitor order accuracy, drink quality and workload throughout the experiment.

OBSERVATION REVEALS A SPECIFIC DELAY

The team traces payment, ticket reading, preparation, packing and handover.

During observation, workers repeatedly pause to clarify unclear milk selections. Staff show how the current ticket groups options ambiguously.

This is a suspected cause worth testing. Other delays are recorded for later investigation so the first test stays focused.

TEST ONE CLEARER TICKET FORMAT

The revised ticket places the selected milk in a consistent, prominent field.

Prediction: clarification requests will fall, with fewer late orders and no increase in wrong drinks.

The shop tests the format across comparable lunch periods. Staff record order volume, staffing, clarifications, late orders and drink errors.

INTERPRET THE ILLUSTRATIVE RESULT

Suppose late orders fall from 18 to 9 per 100, while accuracy holds.

That is a nine-percentage-point reduction, or 50% fewer late orders relative to the baseline. The target of five remains unmet.

Review demand and staffing before attributing the change to the ticket. Continue observation to check whether the improvement persists.

PRESERVE THE LESSON AND CHOOSE THE NEXT TEST

If follow-up supports the ticket's benefit, the shop updates its template and trains staff.

Remaining delays cluster around handover. The next cycle investigates that step.

The team retains the baseline, experiment and result. Future employees can understand both the method and the reason it was adopted.

PERSONAL KAIZEN

APPLY THE LOGIC TO EVERYDAY FRICTION

Choose one recurring difficulty: finding documents, starting study or preparing for tomorrow.

Describe the situation, change one part of the environment and review the result.

The examples in this chapter adapt improvement principles to personal routines. They are suggested experiments, with outcomes that depend on your circumstances.

EXAMPLE: MAKE READING EASIER TO START

Current condition: you intend to read but rarely begin after dinner.

Experiment: place the book beside your usual seat and read two pages after clearing the table.

Record which days you begin and what interrupts you. At week's end, adjust the time, location or task size. Expand only when the routine remains useful and manageable.

EXAMPLE: REDUCE REPEATED SEARCHING

Current condition: you repeatedly search for documents before meetings.

Experiment: keep the agenda and relevant links in one consistently named meeting note.

For a week, record preparation time and missing items. Keep the arrangement if it helps. Review it periodically so old material does not make the system harder to use.

LET IMPROVEMENT SUPPORT A SUSTAINABLE LIFE

Personal improvement can include simplifying a routine, reducing commitments or creating room for rest.

Choose an outcome that matters to you and a review rhythm you can sustain. A missed day provides information about the routine's fit.

Stop tracking when the measurement itself creates more burden than useful learning.

LEADERSHIP, EVIDENCE AND LIMITS

MAKE IMPROVEMENT PART OF PAID WORK

Suggested team routine: reserve a short weekly session to review one recurring problem and authorize the next safe test.

Name an owner and a review date. Give frontline employees a clear route to request help.

When staff raise an issue outside their authority, leadership must address the dependency, resource constraint or policy involved.

EXPLAIN HOW RELEASED CAPACITY WILL BE USED

Before asking people to improve efficiency, discuss what happens to the time released.

Possible uses include reducing overtime, improving service, training or taking on valuable work. Make commitments you can actually honor.

Our management recommendation: include employee workload and participation in the review of each improvement.

KEEP A BALANCED SCORECARD

For a small service team, a suggested scorecard is:

1. Delivery: requests completed on time.
2. Quality: errors or rework.
3. Customer: complaints or satisfaction.
4. People: workload and obstacles.
5. Cost: resources consumed.

Use only measures that inform decisions. Review whether a local gain creates a problem elsewhere.

WHAT RESEARCH CAN TELL US

A JICA working paper studied Kaizen's worker impacts in Central America and the Caribbean using propensity-score matching.

It reported improved working conditions and stronger worker social capital.

The findings are encouraging. Matching is observational and cannot remove all possible unmeasured differences between participating and comparison firms.

KNOW WHEN A LARGER DECISION IS NEEDED

A team can make an unwanted product cheaper to produce. That does not establish customer demand.

Use strategy and customer discovery to decide what is worth doing. Use Kaizen to improve how valuable work is performed.

Major redesign, investment or stopping an activity may be appropriate when small experiments cannot address the underlying problem.

AVOID IMPROVEMENT THEATER

Warning signs include many workshops with no follow-up, suggestion backlogs and targets measured only by the number of ideas submitted.

Ask for a specific problem, baseline, test, result and sustained method.

Also ask who learned to solve the problem. A useful improvement strengthens both the process and the people responsible for it.

YOUR FIRST 30 DAYS

DAYS 1 TO 7: CHOOSE AND OBSERVE

Suggested first-week plan:

1. Select one frequent, frustrating task.
2. Define its start, finish and customer.
3. Observe several real examples.
4. Record time, errors and obstacles.
5. Ask the people involved what they notice.

End the week with one specific problem statement. Keep proposed solutions separate from observed facts.

DAYS 8 TO 14: INVESTIGATE AND PLAN

Review where the problem concentrates. Explore causes with the people doing the work and verify the most plausible explanation.

Choose one small change. Write the prediction, owner, scope, measurement and review date.

Define conditions that would stop the test. Obtain appropriate approval before changing shared or consequential processes.

DAYS 15 TO 21: RUN AND STUDY

Run the agreed test and record what actually happens, including exceptions.

Compare results with the baseline and prediction. Check quality, workload and other safeguards.

If the evidence is unclear, extend or revise the test. Avoid declaring success simply because the first day felt easier or the team likes the idea.

DAYS 22 TO 30: SUSTAIN AND SHARE

Adopt, adapt or abandon the change based on the evidence.

For a useful change, update instructions, demonstrate the method and name a follow-up owner. Share the problem, test and lesson with affected people.

Schedule a later check. Choose the next problem only after responsibilities for sustaining this improvement are clear.

YOUR ONE-PAGE KAIZEN RECORD

Problem and context:
Current measure:
Target and deadline:
Observed evidence:
Suspected cause:
Change and prediction:
Owner and test period:
Quality and workload safeguards:
Actual result:
Decision and reasoning:
Updated method:
Follow-up date:

Keep it brief enough to use. Attach observations when the decision needs more evidence.

STARTUP LESSONS

CHOOSE A REPEATED CUSTOMER FRICTION

Find one recurring obstacle in a valuable customer journey: incomplete briefs, unclear onboarding or delayed handovers.

Combine user observation with process measures. Select a test that can teach you something within a short cycle.

A useful founder question: which repeated difficulty consumes customer effort and creates avoidable work for the team?

IMPROVE THE HUMAN AND AI WORKFLOW TOGETHER

For an AI-assisted process, track corrections, rejected outputs and handoff delays as well as completion time.

Test a clearer input template, validation rule or review step. Keep the surrounding process stable enough to interpret the result.

Assign a human owner for quality decisions. Review whether the change moves extra work to customers or reviewers.

TURN LEARNING INTO A REUSABLE PLAYBOOK

Create a WorkFlow for one improvement cycle: observe, define, investigate, test, review and standardize.

Give each WorkStep an owner, evidence requirement and expected output. Save the validated method and lessons as a StackSlide.

Prompt to start: Help me reduce recurring delays in [process], while protecting [quality measure].

SOURCES AND RESEARCH NOTES

HOW THIS STACKSLIDE USES SOURCES

Historical and technical sections draw on Toyota, JUSE, Kaizen Institute, ASQ, the Deming Institute and Lean Enterprise Institute.

The worker-impact section cites JICA research. Source notes follow.

The coffee scenario, personal exercises, implementation schedule and startup applications are original teaching material, not reported case-study outcomes.

SOURCES: MEANING AND HISTORY

Masaaki Imai: definition, verified quotation and publication history.
https://kaizen.com/masaaki-imai/

QC circles: origins, participation and purpose.
https://www.juse.or.jp/english/qc/index.html

JUSE's international activity: Deming's 1950 invitation.
https://www.juse.or.jp/business/international/

SOURCES: TOYOTA AND THE IMPROVEMENT CYCLE

TPS: daily improvement, jidoka and just-in-time.
https://global.toyota/en/company/vision-and-philosophy/production-system/

PDCA procedure:
https://asq.org/quality-resources/pdca-cycle

PDSA and Deming's learning emphasis:
https://deming.org/explore/pdsa/

SOURCES: PRACTICE AND REFLECTION

Kaizen:
https://www.lean.org/lexicon-terms/kaizen/

Standardized work:
https://www.lean.org/lexicon-terms/standardized-work/

Hansei:
https://www.lean.org/lexicon-terms/hansei/

Gemba observation:
https://www.lean.org/the-lean-post/articles/how-to-go-to-the-gemba-go-see-ask-why-show-respect/

SOURCES: SEEING THE WORK

Value-stream mapping:
https://www.lean.org/lexicon-terms/value-stream-mapping/

Seven original wastes:
https://www.lean.org/lexicon-terms/seven-wastes/

Waste, unevenness and overburden:
https://www.lean.org/lexicon-terms/muda-mura-muri/

SOURCES: INVESTIGATING AND ORGANIZING

5S:
https://asq.org/quality-resources/five-s-tutorial

Pareto charts:
https://asq.org/quality-resources/pareto

Fishbone diagrams:
https://asq.org/quality-resources/fishbone

Five Whys:
https://www.lean.org/lexicon-terms/5-whys/

SOURCES: PEOPLE AND EVIDENCE

Five core principles:
https://fabriq.tech/en/2024/12/17/what-are-the-5-principles-of-kaizen/

Toyota Way:
https://global.toyota/en/company/vision-and-philosophy/code-of-conduct/

JICA worker-impact study:
https://www.jica.go.jp/english/jica_ri/publication/workingpaper/wp_173.html

PEAK PERFORMANCE STARTS WITH BIOLOGY

Kotler defines peak performance as getting our biology to work for us rather than against us.

Underneath performance are systems that shape motivation, learning, creativity, and flow.

FLOW STATE

WHAT IS FLOW?

Flow is an optimized state of consciousness where we tend to feel and perform at our best.

It appears when attention becomes deeply absorbed in the task, until distractions and everything outside the activity seem to fade away.

THE 4 SIGNS OF FLOW

1. Action and awareness begin to merge.

2. Self-consciousness and the inner critic become quieter.

3. Attention becomes intensely focused.

4. Time feels distorted: minutes may feel like seconds, or seconds may feel much longer.

WHY FLOW FEELS SO POWERFUL

Kotler describes flow as involving a powerful mix of feel-good neurochemicals.

That chemical environment is one reason flow can feel rewarding, immersive, and memorable—and why people often want to return to activities that reliably produce it.

FLOW + MEMORY

FLOW CAN STRENGTHEN LEARNING

Deep focus makes experiences easier to encode into memory.

Kotler argues that the neurochemistry of flow also contributes to learning, helping important moments become more strongly remembered.

THINK ABOUT YOUR STRONGEST MEMORIES

Some of our strongest positive memories come from moments when we were completely inside an experience.

A competition. A performance. A trip. A creative breakthrough. A dangerous challenge.

These can carry many characteristics of flow.

WHEN MEMORY BECOMES THE PROBLEM

Kotler describes PTSD in simplified terms as a highly powerful memory that other thoughts and experiences can keep reconnecting to.

His key question: can a new, deeply absorbing experience help create a competing memory strong enough to change that pattern?

FLOW + TRAUMA

THE IDEA: BUILD A STRONG NEW EXPERIENCE

Kotler's argument is not simply 'forget the trauma.'

The idea is to create powerful new experiences with intense attention, positive emotion, challenge, and learning—then use therapy to help integrate them into a healthier psychological pattern.

EXAMPLE: SURFING + TALK THERAPY

Kotler cites an Army program combining surfing with talk therapy.

Surfing contains many flow triggers: immediate feedback, physical challenge, focused attention, risk, novelty, and clear consequences.

Therapy sessions then followed the surfing sessions.

WHY SURFING MAY TRIGGER FLOW

A wave does not allow much mental wandering.

You must read the water, balance, react, and adjust continuously.

That combination of challenge, feedback, movement, and full attention can push the mind toward deep absorption.

WHAT KOTLER SAYS HAPPENED

Kotler says that five weeks of surfing twice a week, combined with regular talk therapy, significantly reduced PTSD symptoms for participants and reduced medication needs in some cases.

Treat this as a claim from the talk, not proof that surfing alone treats PTSD.

FLOW + ADDICTION

FLOW AS AN ALTERNATIVE REWARD

Kotler also points to addiction programs that use outdoor, high-flow activities.

The logic is practical: if the brain is seeking intensity, reward, novelty, and absorption, healthy experiences may provide some of those rewards without relying on drugs.

EXAMPLE: OUTDOOR RECOVERY PROGRAMS

Some rehabilitation programs, especially for young people, use mountains and outdoor challenges as part of treatment.

The goal is not just distraction. It is to create demanding, meaningful experiences that engage attention, effort, emotion, and social connection.

EXPERIENCE AS MEDICINE?

WHAT IF DOCTORS PRESCRIBED EXPERIENCES?

Kotler imagines a future where psychology uses experiences more deliberately.

Instead of only asking, 'Which drug or therapy?' we may also ask, 'Which experience could create the attention, emotion, learning, movement, and connection this person needs?'

HEARTBREAK WORKS THE SAME WAY

After a breakup or loss, ordinary places and objects can repeatedly reactivate memories of the person.

The house. A song. A restaurant. A street.

Kotler's point: the mind may need powerful new experiences to begin building memories that no longer orbit the old relationship.

WHY HE USES SKYDIVING AS AN EXAMPLE

Skydiving is Kotler's extreme example because it rapidly demands total presence.

Fear, novelty, risk, sensory intensity, and immediate feedback can overwhelm ordinary mental chatter and create a deep state of absorption.

THE BIGGER PRINCIPLE

The central idea is bigger than surfing or skydiving:

Our experiences change our brain state.

Brain states influence learning and memory.

So carefully designed experiences may become useful tools for creating new patterns of attention, emotion, and behavior.

IMPORTANT: FLOW IS NOT A STANDALONE CURE

The talk presents an intriguing therapeutic direction, not a universal prescription.

PTSD, addiction, grief, and other mental-health conditions require individualized care. Flow-based activities are better understood as possible complements to evidence-based treatment, not automatic replacements.

FLOW, IN ONE SENTENCE

Flow is more than feeling productive.

It is a state of deep absorption that can intensify learning and memory—and, in Kotler's view, may help people build powerful new experiences strong enough to reshape old patterns.