The Algorithm: Can Hypergrowth Also Build Trust?

Source transparency: This critical review draws on the publisher’s description and excerpt, published chapter listings and available bibliographic material. It does not claim independent access to every page of the complete book or firsthand verification of every corporate case study. The practical examples and recommendations for Haiti are Mole FM’s own analysis, not claims made by the author.

Why this book matters

In a community with limited electricity, uneven internet access, expensive transport and tight budgets, an organization cannot afford to confuse activity with progress. A school may collect forms that nobody reads. A small business may require three approvals for a decision one employee can safely make. A radio station may produce more content without learning whether listeners find it trustworthy and useful.

The Algorithm: The Hypergrowth Formula That Transformed Tesla, Lululemon, General Motors, and SpaceX offers a provocative question: What if the fastest improvement begins not by working harder, but by questioning the rules that created the work? Jon McNeill, a former Tesla president and Lyft executive, translates an approach he learned while working with Elon Musk into a sequence of five operating principles. Published by Portfolio on March 24, 2026, the US hardcover edition is listed at 224 pages.

It is a useful book for people who build and operate things, not only for people who admire large companies. Yet its ambitions need a serious ethical test: Does simplification create durable value for customers, workers and the wider community, or does it merely transfer costs and risks to someone less powerful?

Part I: The five-step algorithm

1. Question every requirement

Start by refusing to treat an existing rule as a permanent fact. Who introduced it, what specific risk does it manage, and what evidence demonstrates its current value? A requirement may be an essential safety measure—or a legacy habit whose original reason has disappeared. The task is not to reject expertise but to require reasons that survive scrutiny.

Local application: A lending organization might ask whether borrowers truly need to submit the same information in two offices. Before deleting an identity check, however, it must understand fraud, consumer-protection and legal obligations. The distinction between waste and safeguard is fundamental.

2. Delete every possible step in the process

Once requirements are challenged, remove actions that create no necessary benefit. Many teams polish steps that should never have existed. A complicated customer form can be made more attractive, but the more meaningful improvement may be to ask fewer questions.

Local application: A resort guest should not need to message three people to confirm an available room. One accountable reservation channel, with a clear receipt and transparent cancellation conditions, may deliver a better experience than another automation tool.

3. Simplify and optimize

Only after unnecessary steps are eliminated does optimization make sense. Standardize clear instructions, make the next action obvious and reduce avoidable handoffs. This order prevents teams from investing heavily in the wrong process.

Local application: Instead of creating an elaborate dashboard for a small community project, begin with one reliable record of requests, completion time, costs and complaints. Build more complexity only when it answers a real decision.

4. Accelerate cycle time

The goal is to shorten the gap between discovering a problem, deciding what to do, testing a solution and receiving useful feedback. Faster cycles expose errors sooner and reduce the cost of waiting. But urgency is not an excuse to pressure employees, skip consent or rush decisions where careful review is the service.

Local application: A radio newsroom may improve turnaround by separating verification, translation and narration into well-defined responsibilities. Publishing sooner is only a gain if facts and meaning survive those steps.

5. Automate last

Automation arrives after the work is necessary, lean and understandable. Otherwise software simply performs waste at machine speed, often making mistakes harder to spot. This is the most immediately relevant lesson for organizations considering AI agents, payment systems or autonomous publishing.

Local application: Before automating an hourly bulletin, define the factual source, freshness limit, copyright checks, pronunciation review, approval policy, correction mechanism and evidence that audio actually plays. Then automate the validated workflow, not the assumptions.

Part II: The three cultural ingredients

The book’s second part moves beyond operational steps to the organizational conditions needed to sustain them. The published contents identify three themes: understanding the customer’s complete experience, building urgency and accountability, and “eating your own dog food”—personally experiencing what your organization delivers.

Expand the product to the entire customer experience

A customer does not experience departments, KPIs or organizational charts separately. They experience the whole journey: finding the service, understanding the price, using it, getting help and resolving an error. A payment app is not successful merely because a transaction clears. It must also be understandable, accessible, reversible when appropriate and supported when something goes wrong.

Make accountability real, without confusing it with fear

Ownership becomes practical when every important task has a responsible person, a deadline and observable evidence of completion. A daily or weekly review can remove obstacles early. The danger is turning every delay into a personal failure or rewarding people for hiding bad news. Healthy accountability makes it safe to report problems while still expecting follow-through.

Use what you build

Leaders should experience their own products and services, particularly points where customers struggle. Call the service line, listen to the station on a low-bandwidth phone, test a checkout, attempt a refund or make an actual booking. Customer observation can reveal friction that polished presentations conceal.

Where the book is strongest

First, it restores the importance of sequence. Many organizations buy new technology before they can explain the problem. McNeill puts interrogation and subtraction ahead of software.

Second, it takes the customer experience seriously. This is a better organizing principle than departmental convenience. A company may report impressive internal efficiency while imposing confusion on its users.

Third, the framework is teachable. Even a team of three can work through the questions together. The five steps make complexity visible, give people a shared vocabulary and encourage small tests rather than endless meetings.

Fourth, it gives established practices no immunity. An organization can respect expertise while demanding a fresh explanation of an inherited rule. This can free scarce money, attention and talent for more useful work.

Where readers should challenge McNeill

Growth figures do not prove which action caused growth

The publisher highlights an increase in Tesla revenue from about $2 billion to $20 billion during McNeill’s tenure, over 30 months. That is a promotional account of an extraordinary period, not by itself a controlled demonstration that the five-step framework caused the increase. Product demand, investment, market conditions, leadership decisions and other factors matter too. Case studies teach possibilities; they do not supply guaranteed forecasts.

Fast is not always better

A delayed hotel confirmation is waste. A delayed medication check, investigative correction or suspicious financial transfer may be essential protection. Leaders should reduce avoidable waiting, not celebrate the removal of every pause.

Cost reduction can move costs onto others

A company may report savings because customers now fill out lengthy forms, employees work unpaid hours, or suppliers bear greater risk. This is not genuine system improvement. Measure the full cost to people affected, not merely the budget line of the organization making the change.

Large-company examples need adaptation

Small Haitian businesses cannot assume the financing, infrastructure, supply chains or market power of Tesla or General Motors. The practical question is which principles remain useful at low cost. Often the answer is a clear owner, a shorter process, transparent records and a small reliable experiment.

Ethics must be designed into the algorithm

Questioning requirements should not become a license to erase labor rights, safety controls, accessibility provisions, privacy obligations or meaningful editorial review. A requirement can feel inconvenient precisely because it protects a person whose interests are easy to overlook.

Applying the ideas in Môle-Saint-Nicolas

These are proposed tests, not verified improvements or financial predictions. An efficient process that nobody wants is still a failure. Ask customers directly and record unfavorable feedback.

A 30-day blueprint: one valuable improvement

Days 1–7: Observe and question

Choose one real service. With permission, ask five users and two frontline workers where time, money or trust is lost. Draw the complete path from first contact to completed outcome. Identify every approval, field, delay and manual transfer. Write down which steps protect safety, rights, money or accuracy; do not remove them by intuition.

Days 8–14: Delete and simplify

Choose one low-risk step that appears redundant. Test a shorter version with a small group. State who owns the decision, what information is essential and how to reverse the change if it harms people. Publish transparent prices or service promises where relevant. No spending is required to begin.

Days 15–21: Shorten the learning cycle

Track the time needed to deliver a real result. Review failures each day or week as appropriate. Ask customers what became easier and what became harder. Keep a correction and escalation path open. Improve instructions before considering automation.

Days 22–30: Decide whether to automate

Only automate a stable, repeatedly tested step. Define a responsible human, an error threshold, a manual fallback and an audit record. Compare the result to the first week. If time fell but complaints or errors rose, the experiment did not pass. Keep, revise or reverse it according to evidence.

Questions for a family, classroom or team discussion

1. Which rule do we follow simply because somebody once told us to?
2. Which requirement seems annoying but protects someone who cannot easily speak up?
3. What would customers remove from our process if we watched them use it?
4. When has a fast decision created expensive rework?
5. What would we stop doing tomorrow if our goal were genuinely useful service rather than impressive activity?
6. How will we know that automation increases freedom and opportunity instead of only cutting staff time?

Final assessment

8.5 out of 10. The Algorithm offers an unusually memorable operating framework. Its insistence on asking hard questions, deleting unnecessary complexity and delaying automation deserves attention from leaders across sectors. Read it as a practical method for experiments, not as proof that every organization should imitate a high-pressure technology company. The best leaders will borrow the sequence while adding the protections the sequence alone cannot guarantee.

For Mole FM listeners, the takeaway is simple: start small, identify one real burden, fix it with the people affected, and measure the result honestly. Innovation is not simply moving faster. It is making life better.

Sources and additional reading

1. McNeill, J. (2026). The Algorithm: The Hypergrowth Formula That Transformed Tesla, Lululemon, General Motors, and SpaceX. Portfolio. Publisher overview and US edition details: Penguin Random House.
2. Publisher excerpt and table of contents: Penguin Random House Retail.
3. Published table of contents and preview details: Everand.
4. Bibliographic cross-reference: Google Books.

Editorial note: This is an independent review, not an endorsement of any company or individual mentioned in the book. Illustrative applications and the 30-day plan are original Mole FM recommendations. No sponsorship or affiliate purchase claim is made. The cover-style graphic above is an original editorial treatment, not a reproduction of the publisher’s cover.