Write each lowlight as an experiment loop: we did A (in our control), hoping for B; we got C; we now believe D; next we do E, hoping for F. Do not report skipped work you controlled, weather you could not control, or “it got complex” with no cut. Highlights are A hoping for B and getting B. Lowlights are the same skeleton with C instead of B, plus the thinking. That record is what early investors underwrite.

Should I send stakeholder updates at all?

Yes, if you want a clearer window into how you think. Send them consistently with highlights and lowlights. If you already do this, you are ahead of most funded founders I know. Most companies with real investors go quiet. Sending is the entry fee. The lowlight craft is where almost everyone fails.

What are examples of weak lowlights?

Three I hear constantly: we did not run interviews this week; development is slower because our architect is retiring; the pivot got too complex for beta. People guess “not enough learning” or “not vulnerable enough.” The real failure is control. Skipped interviews are time management, not a lowlight. A retirement outside your control is context, not the learning. “Complex” is not a finding when you chose the pivot.

What does a good lowlight look like to start?

A team thought they could save customers $30 a month. They ran twenty-five interviews in two days. The real number was about $10. That is the start of a good lowlight: controllable action, clear hope, ugly numbered result.

How can a miss be “good” if I cannot control outcomes?

Actions and outcomes are different. You fully control the experiment you run. You do not control whether the world returns B. Keep the line: you do not control outcomes; you control the next experiment. Your lowlight should be about what you did.

What is the A through F formula?

• A. What we did, in our control.

• B. What we hoped would happen.

• C. What actually happened.

• D. What we now believe because of the B-C gap.

• E. What we do next, chosen because of D.

• F. What we hope happens from E.

Next update, E and F become the new A and B. That is why it compounds.

How do I finish the $30 example?

We did 25 interviews over two days, hoping most would confirm about $30 a month in savings. Nearly all came in at $10 or less. We now think savings are too thin at this price for this customer. Next we do X hoping for Y: mine transcripts for another profile, run fifteen more interviews, or pivot. I am not judging which X. I am buying the thinking.

What is the difference between a highlight and a lowlight?

A highlight is we did A hoping for B and we got B. You can skip the method. You are a magician; we got B. A lowlight is we did A hoping for B and we got C. Now show D, then E→F.

Can you give two short full loop examples?

Pickup game: we texted 60 people 40 minutes ahead, hoping 15 would show. We got 22 thank-yous and 3 who showed. We now think same-day pings miss planners. Next we run a Sunday poll and only book Tuesday if we get 8 yeses, hoping for one night we do not chase.

Study planner: 180 signups, 40 used it last month. We emailed 140 dormant users hoping 40 would reopen that week. 12 opened, 3 opened the app, 0 returned next day. Stickiness clustered in two project-heavy classes. We now think blasts do not create habit; retention follows weekly deadlines. Next we get onto syllabi for the next assignment cycle, hoping 50 people use it twice.

What does not belong in a lowlight?

Shocks that teach nothing about the business, and raw mood. A hospitalization should be told to people. It is not an experiment loop. When something outside your control hits, name it, then reframe into a controllable next experiment (for a retiring architect: how we hire and structure stay).

Should cold audiences see a wall of lowlights?

No. For Demo Day and cold rooms, lead with remarkable. Keep full A-F for people already in the loop. See the Demo Day guide.