Entrepreneurship: Hawthorne in Management, Product, and on Yourself

The founder is a supplier of gaze

A founder has many roles: visionary, recruiter, seller, accountant, engineer, communicator. One of their most underrated roles is also the cheapest: they supply gaze. They observe — and their observation reshapes the performance, morale and trajectory of the people they watch.

Steve Jobs spent hours in Apple's design department, watching the details. That presence — without a word — raised the quality bar of the entire department. Bezos used to write to the 1 % of customers who had complained and forwarded the email to the relevant team with a "?". That single practice calibrated Amazon's "customer obsession" standard for two decades.

A founder cannot do everything. But what they look at, the organisation ends up prioritising.

The Hawthorne effect is, for a founder, the cheapest and most powerful steering tool.

Hawthorne management: the rituals that work

A manager who wants to activate the Hawthorne effect without surveilling must build rituals that make the gaze structurally present and benevolent.

The weekly 1:1

The 1:1 is not a progress meeting. It is an observation ritual: for 30-45 minutes, the report has the manager's complete attention. That attention:

• Activates public self-awareness
• Reinforces the feeling of being seen
• Creates a regular feedback loop

1:1s that work have 3 properties:

1. Regular and held: cancelled < 5 % of the time.
2. Asymmetric: the report brings the agenda.
3. Cumulative: a minimal log of each session is kept.

The walking review

Three times a week, the manager walks around (or runs a Slack pulse if remote): "what are you working on this morning? any blocker?". No judgement, no evaluation. Just a signal: "I know what you're doing".

Psychological effect: simply knowing that someone will know activates public self-awareness. Day-to-day trade-offs rise in quality.

The weekly show-and-tell

Every team member presents, in 5 minutes, an artefact produced that week: a feature, a signed deal, a well-crafted email, a half-finished design. Rotation makes observation visible and valorising.

Five effects:

• Hawthorne on the presenter
• Hawthorne on those expecting their slot next week
• Alignment on the team's definition of "good"
• Early detection of drift
• Sense of belonging

The monthly KPI retro

Once a month, the team gathers around 3 or 4 strategic indicators. Everyone comments: "here's what moved, here's why". The manager asks 2 precise questions, no more.

That ritual keeps a Hawthorne alive without policing: everyone knows they will have to discuss their indicator. Preparation alone drives sustained effort during the month.

Product-as-observer: Hawthorne in UX

A well-designed application observes its user. Not to surveil, but to return a mirror that activates public self-awareness and triggers behaviours aligned with their objectives.

Iconic example: Duolingo and the streak. Simply displaying "47 days" triggers powerful self-observation. When the user loses their streak, what hurts isn't the loss itself — it's having lost a visible status.

Case study: a B2B SaaS that changed a single screen

A project-management software vendor (target users: IT team managers) ran a simple test. On their dashboard, they added a small widget:

"7 people in your organisation use this feature regularly"

Measured effect over 4 weeks:

• Feature activation by exposed users: +62 %
• 30-day retention: +18 %
• Product NPS: +11 points

No product change. Just a signal: "others like you are watching what you do". Pure Hawthorne.

The Hawthorne trap: enterprise-scale Goodhart drift

A leader who discovers the Hawthorne effect is tempted to measure everything. That is a structural mistake. Four classic drifts:

1. The vanity metric

Measuring what looks good rather than what matters. Number of followers instead of conversion. Tickets closed instead of customer satisfaction.

2. Over-measurement

20 KPIs displayed → 0 KPI prioritised. The team plays whatever it likes. Rule: 3-5 public KPIs, never more.

3. The frozen KPI

The same public KPI for 24 months → it gets gamed without thinking. Rotate what you observe every 6-9 months.

4. The KPI without qualitative

Measuring opportunity count, but not pipeline quality. Tracking NPS without reading verbatims. Always combine a quantitative and a qualitative.

Living OKRs: a Hawthorne by construction

OKRs (Objectives & Key Results), well practised, are a pure Hawthorne device.

But: an OKR practised as a performance contract slides into Goodhart. The secret:

• Target scoring around 0.7 (don't aim for 1)
• No direct OKR ↔ bonus link
• Review focused on learning, not sanction
• Freedom to redefine a mis-calibrated KR

Founder Hawthorne: watching yourself

The hardest, and often most valuable, Hawthorne effect for a founder is the one they exert on themselves. Three high-impact self-observation practices:

1. The weekly journal

Thirty minutes on Friday answering 5 questions:

• What did I spend time on this week?
• What should I have spent time on?
• Which decision did I make that I'm unsure about?
• Which decision did I avoid making?
• What concrete action will I take Monday?

Writing anticipates a future re-read (by yourself, in 3 months or a year). That anticipated re-read is a self-Hawthorne.

2. The mentor / sparring partner

Once a month, 90 minutes with someone who asks sharp questions. The founder spends the previous week preparing — i.e., watching themselves.

Typical effect: 30-40 % better clarity on structural decisions.

3. The board / advisor

A serious board requires a monthly or quarterly board pack. Preparing it forces the founder to systematically observe KPIs, team morale, burn, product progress.

No board? Invent one. Three trusted people who receive a monthly structured email. Simply writing that email produces a founder Hawthorne.

The installation sequence in a startup

If you start from zero, here is a proven trajectory to install a healthy Hawthorne system.

Month 1 — Diagnosis

• List the observation rituals already in place
• Identify 3-5 KPIs that should be public
• Pick 1 or 2 priority zones (often: sales)

Month 2 — Core rituals

• Generalise weekly 1:1s
• Set up the weekly show-and-tell
• Publish 3 key KPIs on a visible Slack channel

Month 3 — Observed coaching

• Start weekly call review (1 call per rep)
• Stabilise a scoring grid
• Roll out the personal logbook

Months 4-6 — AI and scale

• Deploy a conversation intelligence stack
• Automate post-call feedback
• Sign an ethical observation charter as a team

Month 7+ — Qualitative steering

• Rotate KPIs every 6-9 months
• Measure feedback application rate
• Introduce listening to the manager's calls by the team (symmetry)

The ultimate test: does your team talk about it when you're not there?

The best Hawthorne is not the one that fires when you're present. It's the one that keeps working when you're not.

Three signs of a healthy Hawthorne internalised in the culture:

1. Reps re-listen to their own calls, unprompted.
2. Indicators are looked at and discussed in Slack threads without a manager pushing.
3. Peers challenge each other, without vertical hierarchy.

If those three signals are present, you have turned a top-down Hawthorne (manager → team) into a horizontal Hawthorne (team ↔ team). That's what separates an organisation that performs from one that surveils itself.

Founder Hawthorne — architecture summary

                    ┌─────────────────────────┐
                    │   FOUNDER               │
                    │   - Weekly journal      │
                    │   - Monthly sparring    │
                    │   - Board pack          │
                    └────────────┬────────────┘
                                 │
                ┌────────────────┼────────────────┐
                ▼                ▼                ▼
        ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
        │ MANAGEMENT   │ │ PRODUCT      │ │ SALES        │
        │ - 1:1        │ │ - Dashboard  │ │ - Call review│
        │ - Show&tell  │ │ - Streaks    │ │ - Conv. AI   │
        │ - KPI retro  │ │ - Recap email│ │ - Logbook    │
        └──────────────┘ └──────────────┘ └──────────────┘
                │                │                │
                └────────────────┼────────────────┘
                                 ▼
                    ┌─────────────────────────┐
                    │   TEAM                  │
                    │   Horizontal Hawthorne  │
                    └─────────────────────────┘

Ready-to-use AI prompt: org-wide Hawthorne audit

You are an expert in the Hawthorne effect and commercial/managerial steering.

Here is a description of my organisation:
[COMPANY DESCRIPTION, TEAM, CURRENT TOOLING]

For each zone (management, sales, product, marketing, founder), score:
1. Current observation level (1-5)
2. Feedback loop quality (1-5)
3. Goodhart risk present (1-5)
4. Risk of dehumanising surveillance (1-5)

Conclude with:
- Overall diagnosis (score /20)
- The 3 rituals to install in priority
- The 2 risks to anticipate
- A 90-day action plan

Summary

A founder is, for their organisation, a supplier of gaze. Well-orchestrated Hawthorne rituals — 1:1s, show-and-tell, KPI retro, public dashboards, call review, living OKRs — produce a system where each person feels seen, without hostile surveillance. AI lets you industrialise that gaze at scale, and the founder must subject themselves to observation devices (journal, sparring, board) to stay aligned with their own vision. The ultimate sign of a healthy Hawthorne is horizontalisation: when the team challenges each other without the founder, the culture has internalised observation as a method of improvement. You now have the tools to turn a hundred-year-old psychological mechanism into a durable competitive advantage — provided you handle it with ethics, transparency, and patience.