Operating by John Brewton

Join 30K+ operators and strategic professionals as this Harvard-educated econ & business nerd decodes the future of business. Get career-changing insights that challenge conventional thinking and equip you to build tomorrow's companies.

Writer & Founder

6A East Partners

Delivered 25–50% net profit growth and 10–15% revenue increases for clients through operational optimization, headcount reduction (25–79%), and implementation of AI-native business models.
Designed and implemented custom AI tools (ChatGPT, Anthropic Claude, Google Gemini, Meta LLAMA) integrated via APIs, significantly enhancing client decision-making, sales productivity (10x improvement), and operational efficiency.

Developed and executed comprehensive continuous-improvement frameworks, advanced performance-management systems, and transparent, quantitative hiring processes utilizing industrial psychology assessments.

Integrated Python and Google Apps Script for enhanced automation, accuracy, and reporting efficiency.

Expertly employed Tableau and Power BI to deliver powerful, actionable analytics, transforming complex data into strategic narratives.

Founder & CEO

R.G. Brewton, Inc.

Increased company revenue and EBITDA through strategic automation, data-driven decision-making, and strict financial discipline (no external investors/private equity).

Built internal engineering teams, leading custom ERP and real-time data warehousing projects, automating all warehouse operations, and achieving <0.75% shipping error rate.
Managed $50M+ annual inventory purchases through innovative direct-shipping strategies from a single, strategically optimized 12,000 sq. ft. facility (10x smaller than industry standard).

Expanded operations internationally into Mexico and Costa Rica, managing incorporation, compliance, trade regulations, hiring, and logistical complexities.

CEO - Company was sold to Stellar Industrial

Directed significant operational restructuring, reducing headcount by 40% while growing revenue over 100% through role specialization and advanced automation.

Partnered with industrial psychologists to design specialized roles, significantly reducing operational errors and enhancing productivity across sales, purchasing, sourcing, and inventory management teams.
Designed foundational data automation systems and real-time analytics dashboards, eliminating hundreds of employee hours weekly.

Oversaw domestic expansion, establishing new operations across the Midwest and South, managing geographically dispersed teams effectively.

Director of Operations

Initiated company-wide task automation using macros and Microsoft Power Pivot, saving 200+ hours weekly and increasing profitability by 20% through enhanced operational efficiencies.

Operations Analyst

Developed strategic sourcing relationships with global OEM partners enhancing sourcing efficiency and responsiveness.

Sourcing Specialist

• Tutored college and graduate students in introductory and intermediate micro and macro economics.
• Developed customized lesson plans to cater to individual student needs and learning styles.
• Implemented real-world examples to help students understand complex economic concepts.

Economics Tutor

Harvard University

• Authored impactful public remarks and communications as a vital member of the Office of the Assistant to the President.
• Managed teams of interns for project creating a new mapping of the entire campus.

Communications Specialist

John’s Rock & Roll Dream, Inc.

Gig & Session Drummer

John's Rock & Roll Dream, Inc. 

Drum Teacher

Cross-functional operations leader with a Harvard Economics degree and a PhD in Economics from the University of Chicago. I help organizations scale efficiently by combining commercial strategy, advanced systems, and team alignment.

I’ve led companies through rapid growth, international expansion, and large-scale transformation, delivering measurable financial and operational results. My focus is on building adaptable systems, integrating AI-native solutions, and aligning stakeholders around data-driven decision frameworks.

Key achievements:
→ Scaled a B2B inventory management firm from $25M to $75M while expanding into international markets
→ Negotiated and structured 7–8 figure Fortune 500 contracts
→ Implemented enterprise systems and automated workflows, cutting cycle times and driving operational efficiency
→ Designed AI-enhanced workflows (pricing intelligence, candidate evaluation, productivity automation) that delivered measurable business outcomes

I bring both strategic vision and operational rigor, combining analytical depth with relationship-building to lead distributed teams across regions and time zones.

Core strengths:
→ Competitive operating & go-to-market strategy
→ Cross-functional team orchestration
→ Enterprise system & workflow automation
→ AI-driven operational scaling
→ International expansion & P&L growth

I share insights on these themes in my newsletter Operating by John Brewton, exploring how companies can evolve and thrive in the AI-enabled future of work.


IN-OFFICE WORK MATTERS. Remote work isn’t the debate to have. The real value is in building autonomous teams. 

In-office work speeds trust, accelerates learning, and strengthens culture. It is my default for most teams most of the time, and my strong personal preference. 

But the real question is not remote vs. office, 
it is AUTONOMY. 

Spotify’s line reads like a policy on place, yet it is really a stance on treating adults like owners. 

Location becomes a tactic once autonomy is the value. Autonomy requires an operating system that makes work legible, accountable, and fast. 

When those conditions exist, the office amplifies collaboration, and remote deepens focus. Without them, either mode collapses.

What must be true to earn autonomy?

↳ Outcomes over activities. Define results, scope, and the “definition of done.”
↳ Cascaded goals. Company, team, and role goals connect cleanly with dates and measures.
↳ Decision rights. Who decides, who inputs, who executes, and who is informed are explicit.
↳ Clear cadence. Weekly priorities, monthly reviews, quarterly bets, all tied to outcomes.
↳ One source of truth. Plans, SOPs, and dashboards live where everyone can see and edit.
↳ Write first. Use tight memos for context and decisions, keep meetings for debate or commitment.
↳ Service levels. Response times, handoffs, and quality bars are stated and met.
↳ Role interfaces. Boundaries and touchpoints between teams are mapped like APIs.
↳ Tool minimalism. Fewer apps, deeper mastery, real integrations.
↳ Telemetry. Leading and lagging metrics, visible and reviewed on a schedule.
↳ Guardrails by design. Security, privacy, and compliance built into workflows.
↳ Manager as multiplier. Prioritize, coach, and remove blockers, do not redo the work.
↳ Talent density. Hire for judgment, raise the bar, act quickly on gaps.
↳ Learning loops. Retros, postmortems, and customer signals drive updates to playbooks.
↳ Consequences and praise. Autonomy is earned with performance, protected with accountability.

When these are present, autonomy thrives in any setting. The office is then a choice, not a crutch. Remote becomes a privilege that compounds output, not a shield from inspection. Your job as an operator is to build the conditions so adults can operate, develop, and own results, wherever they sit.

Run these three moves this week:

✅ Publish a one-page Operating Contract for your team, outcomes, cadence, decision rights, SLAs, tools.
✅ Replace one recurring meeting with a concise written update that ends with a clear next decision.
✅ Stand up a simple scoreboard, three to five leading metrics reviewed at the same time every week.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewtonfor deep dives on the history and future of operating companies (🔗in profile).

John Brewton

Operating Strategist 📝Writer @ Operating by John Brewton 🤓Founder @ 6A East Partners ❤️🙏🏼 Husband & Father

No alternative text description for this image

Jack Welch couldn’t stand 
the “Neutron Jack” nickname. 


He felt it a fundamental misunderstanding of who he was. He and Andy Grove are my two favorite leaders and operators. 

For many, his name conjures images of ruthless cost-cutting, mass layoffs, and a shareholder-first obsession. The “Neutron Jack” caricature has overshadowed a more complicated truth.

Here are five of his most notable achievements: 

1️⃣Total shareholder return under Welch was approximately 2,504% from 1984 to 2001, significantly outperforming the S&P 500 over the same period.

2️⃣ Annual revenues grew from about $26.8 billion in 1980 to nearly $130 billion by 2000, a nearly fivefold increase.

3️⃣ Net profit grew from $1.5 billion to $15 billion during his tenure.

4️⃣ Welch pioneered widespread adoption of Six Sigma, improving quality and operational efficiency.

5️⃣ He abolished the nine-layer management hierarchy, promoting a flatter organizational structure with greater agility.


Welch was a teacher. Welch was an operator who believed that the real job of a leader was to shape people and culture. 

↳ Yes, he cut costs. But his real mission was removing bureaucracy. He believed complexity killed performance.

↳ Yes, he demanded performance. But he also invested heavily in training, development, and candid feedback. GE’s Crotonville leadership institute became a model for corporate learning.

↳ Yes, he set high bars. But he also taught leaders that their primary role was to grow others, not themselves.

Leadership is not about the crown. 
It’s about the classroom.

Welch’s legacy, like all legacies, is mixed. Some of his methods don’t translate well to today’s business climate. But his insistence on leaders as teachers, on candid conversations, and on meritocratic growth still holds.

Too often, managers believe their job is to protect authority, defend turf, or polish their own image. Welch flipped that. The job was to make other people better.

Leaders are not coronated. 
They are held accountable.

If you’re in a leadership role today, don’t chase the crown. Build the classroom.

✅ Cut bureaucracy so your team can focus on what matters.
✅ Invest time in teaching, coaching, and feedback.
✅ Measure your success by how well your people grow, not by the shine of your title.

Do this and you’ll avoid the trap of misunderstanding Welch’s true lesson: leaders are responsible for unlocking potential, not guarding privilege.

✅ Do. Fail. Learn. Grow. Win. 
✅ Repeat. Forever.

♻️ Repost & follow John Brewton for content that helps.

📬 Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗 in profile).

Stop being inauthentically “nice.” 
Be authentically kind.

Niceness avoids discomfort. It’s easily becomes inauthentic. Authentic kindness faces what’s uncomfortable with respect. 

Trust scales when leaders choose clarity over comfort. If you want a stronger culture, faster decisions, and fewer surprise failures, practice these shifts daily. 

Here is the operating version of “Nice vs. Kind” for builders and managers from my friend George Stern and his incredible infographic (be sure to give him a follow):

1️⃣ “I won’t bring it up.”
↳ “I’ll share feedback directly so you know where you stand.”

2️⃣ “I’ll agree with the majority.”
↳ “I see it differently, here is why.”

3️⃣ “That’s just how it is.”
↳ “We do not have to accept that. What could we change?”

4️⃣ “I’ll wait and see what happens.”
↳ “Let’s deal with this early before it gets bigger.”

5️⃣ “That’s fine for now.”
↳ “This is a good start. What would make it stronger?”

6️⃣ “I’ll pretend that does not bother me.”
↳ “I need to be honest. Here is what is not working for me.”

7️⃣ “Let’s avoid making waves.”
↳ “Let’s ask the hard question now instead of later.”

8️⃣ “I’ll smooth this over.”
↳ “I’ll say what is wrong so we can fix it.”

9️⃣ “Let’s just celebrate the good part.”
↳ “Let’s celebrate, and also note what we could do better next time.”

🔟 “I do not want to bother you.”
↳ “This is important. When is a good time to talk?”

1️⃣1️⃣ “I will keep quiet.”
↳ “I have an idea that could help. Can I share?”

1️⃣2️⃣ “That’s interesting.”
↳ “Tell me more. I want to understand what you mean.”

How to practice kindness without drama:

↳ Lead with facts, then effects, then a request. Situation, impact, ask.
↳ Write first. Short notes beat vague speeches.
↳ Separate people from problems. Respect the person, challenge the work.
↳ Timebox tough talks. Fifteen minutes, clear purpose, next step documented.
↳ Use default scripts. “Here is what I see, here is the risk, here is my proposal.”
↳ Close the loop. Confirm what was heard, what changes, and by when.

Kindness is not softness. 
It is service. 

It protects customers, teams, and cash by removing ambiguity. Niceness keeps the peace today and creates bigger fires tomorrow. 

Clarity is a gift. Give it early, give it often. 

Start here today:
✅ Pick one shift above and practice it in your next meeting.
✅ Write a 3-line “kind script” for feedback, then use it this week.
✅ Start a simple decision log and share it with your team by Friday.

♻️Repost & follow John Brewton for content that helps.

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

🟧 Do. Fail. Learn. Grow. Win.
🟧 Repeat. Forever.

EQ isn’t about vibes. 
It’s about productivity and workflow. 

Emotionally intelligent leaders aren’t magically calm. They run a day that lowers reactivity and raises judgment. Systems first, feelings follow.

Here is a practical, mobile checklist you can use today:

1️⃣ Prep the night before
↳ Lay out clothes, pack your bag, pre-write the top 3.
↳ Start at 80 percent, finish fast. No morning scramble.

2️⃣ Arrive early, always
↳ Ten minutes buys attention, patience, and options.
↳ Calm becomes routine, not luck.

3️⃣ Schedule what matters
↳ If it matters, it gets a block.
↳ “I’ll find time” means “it won’t happen.”

4️⃣ Automate the repeats
↳ Auto-pay, canned replies, templates, saved prefs.
↳ Spend thinking on decisions, not maintenance.

5️⃣ One list, one brain
↳ Capture tasks in a single trusted place.
↳ Fewer lists, fewer misses, faster handoffs.

6️⃣ Capture, then forget
↳ Jot ideas instantly, move on.
↳ Your head is for thinking, not storage.

7️⃣ Leave white space
↳ Hold open time daily.
↳ Room to re-plan beats perfect plans.

8️⃣ Build buffers
↳ Add 15 minutes between meetings.
↳ Stress falls, quality rises, follow-ups ship.

9️⃣ Sync weekly
↳ Align calendars and priorities with team and family.
↳ Small misalignments compound into fires. Prevent them.

🔟 Protect deep work
↳ Guard one focused block. Phone away, inbox closed.
↳ Outputs over motion, results over noise.

Why this works 💡
↳ Structure lowers cortisol and increases clarity.
↳ Fewer transitions mean fewer errors.
↳ Predictable cadence frees empathy for people, not logistics.

Make this system yours: name the blocks, set the reminders, and keep the rules short. When the day is predictable, your reactions are measured and your team trusts your consistency. EQ is not a personality test score, it is a daily operating design that reduces friction and multiplies judgment under load.

Leaders who practice these habits ship more real work, have fewer avoidable fires, and show up with energy when it matters. Start small, lock in the gains, and let compounding work its wondrous magic. 

✅ Choose two habits and install them this week.
✅ Put them on your calendar with alerts.
✅ Review on Friday, keep what worked, cut what didn’t.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Silos don’t kill productivity. 
Leaders who enable them do.

That’s the truth too many organizations avoid.

Silos are not inherently bad. In fact, specialization and focus often require them. Accounting needs its processes. Sales needs its systems. Product needs its rhythm. Silos give teams structure, clarity, and speed.

The problem comes when leaders fail to connect those silos around shared goals.

Without bridges, you don’t get collaboration—you get fragmentation. You don’t get alignment—you get duplication, miscommunication, and politics.

And the real waste isn’t just lost productivity. It’s lost trust.
↳ Teams start optimizing for their own metrics.
↳ Communication turns defensive instead of cooperative.
↳ Decisions slow down because no one sees the whole picture.

Leaders often say, “We need to break down silos.” That’s the wrong diagnosis. You don’t need to destroy silos—you need to connect them.

The leader’s job is to build bridges:
↳ Define a shared goal that everyone sees as the priority.
↳ Create clear rules of engagement for cross-team decisions.
↳ Design information flow so the right data reaches the right people at the right time.

When you don’t do this, you leave people to figure it out themselves. That’s when individuals end up paddling in circles in the waters between departments—working hard, but not moving the company forward.

Here’s the shift: stop blaming silos, start owning the leadership challenge. The moment you align silos to a common mission, they become assets. The moment you don’t, they become liabilities.

If you’re a founder, operator, or leader—look closely at your company right now:
Are your silos serving your shared goal, or are they serving themselves?

Because silos don’t kill productivity. Leaders who enable them do.

✅ Clarify the one shared goal that takes priority over departmental wins
✅ Build structured bridges for collaboration (decision rules, not endless meetings)
✅ Design systems of transparency so every team sees the same scoreboard

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Learn or earn. 
Either is fine. Both is best. 
If it’s neither, move.

This quote works because it turns career fog into a rule: compound skills + compound cash flow = freedom.

Use this lens:

→ The Learn Zone

Are you stacking durable skills that travel across roles?

Examples: strategy, hiring, selling, pricing, forecasting, negotiating, writing, analytics, ops design.

→ The Earn Zone

Are you tied to revenue, cost, or risk?

Can you point to a weekly metric you move on the P&L?

Micro‑audit for any role
→ What skill is compounding 1% this week?
→ What number am I responsible for?
→ What would break if I vanished for a week?

If you have one zone, the trade can make sense.
If you have both, you’re compounding.
If you have neither, you’re donating time.

Common blockers (and fixes):

1️⃣ You’re “busy” but not learning.
→ Fix: take work with end‑to‑end ownership. Define the problem, the metric, and the deadline.

2️⃣ You’re learning but the value isn’t priced.
→ Fix: frame your work in business terms. Tie it to revenue, cost, or risk. Propose milestone‑based comp.

3️⃣ You’re earning but plateaued.
→ Fix: trade some cash for skill reps. Lead cross‑functional work, take gnarly postmortems, run retros.

4️⃣ Culture hides the score.
→ Fix: make a one‑page P&L map. Line your tasks to a metric.

5️⃣ You’re stuck deciding.
→ Fix: run a 90‑day experiment with two bets—one to deepen learning, one to raise earning—then choose.

If the quote nudged you, don’t let week drift. Use it to filter meetings, projects, and offers. Keep what compounds. Cut what doesn’t. Act now.

Three moves to run today:
✅ Write two columns—Learn and Earn—and list what you actually did last week under each. If a column is empty, mark it.
✅ Pick one metric you can influence in 7 days (revenue, cost, or risk). Define one action that moves it and schedule it.
✅ Choose: stay and redesign your role, change teams, or exit. Put the decision date on your calendar, then execute.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Great companies grow stronger through crisis. 
Fragile ones collapse.

Andy Grove put it plainly:
“Bad companies are destroyed by crisis. Good companies survive them. Great companies are improved by them.”

What Grove observed, 
Nassim Taleb later named: antifragility.

Fragile systems break under stress.
Resilient systems withstand stress.
Antifragile systems gain from stress.

Grove saw it in Silicon Valley’s downturns. Taleb codified it into a general law: volatility, randomness, and shocks aren’t only threats—they can be catalysts for improvement.

Real-world examples prove it:

↳ Toyota during the oil crisis: Rising fuel costs pressured automakers. Toyota’s lean manufacturing system didn’t just absorb the shock—it used it to refine efficiency and leapfrog competitors.

↳ Amazon after the dot-com bust: Where others folded, Amazon doubled down on infrastructure and logistics, setting the stage for AWS and long-term dominance.

↳ Bridgewater during financial crises: Instead of hiding mistakes, the firm’s radical transparency turned stress tests into system improvements, strengthening decision-making across the organization.

Antifragility in business shows up in three patterns:

↳ Feedback Loops: Stress becomes signal. Great companies create mechanisms (andon cord, Amazon memos) that make learning automatic.
↳ Optionality: Keep multiple paths open. A portfolio of bets beats a single fragile plan.
↳ Decentralization: Local adaptability beats centralized rigidity. Teams closest to problems solve them fastest.

The difference is subtle but decisive.

Resilience is survival. 
Antifragility is improvement.

Grove knew it. 
Taleb named it. 
Operators must practice it.

✅ Build systems that turn stress into information, not silence.
✅ Preserve optionality so shocks open doors instead of closing them.
✅ Decentralize decision-making so adaptation happens at the edge, not only at the top.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in comments).

Winning is a lagging indicator. 
Preparation is the leading signal. 

Charlie Munger’s line reminds us: the trophy belongs to whoever invested more in the boring work that happens before the moment. Not motivation or hype. 

Just boring, disciplined, preparation. 

Here is what the “will to prepare” looks like across the operating stack:

1️⃣ Standard operating preparation
↳ Write the play, then run the play.
↳ Simple SOPs, checklists, triggers, and handoffs.
↳ Clear owners and start-to-finish definitions of done.
↳ Pre-mortems that name failure modes before they happen.

2️⃣ Meeting preparation
↳ A memo or pre-read, not a slideshow.
↳ Decision, inputs, constraints, and a deadline stated up front.
↳ Attendees know their role: DRI, recommender, approver, or observer.
↳ Notes captured in the system that work uses tomorrow.

3️⃣ Team preparation
↳ Role clarity, on-call calendars, and escalation paths.
↳ Rehearsals for launches and resets after misses.
↳ Cross-training that reduces single-point risk.
↳ Daily standups that surface blockers early.

4️⃣ Data preparation
↳ One source of truth with defined metrics.
↳ Clean inputs, named owners, and refresh cadence.
↳ Dashboards that answer the next decision, not every curiosity.
↳ Logs that let you audit and learn fast.

5️⃣ Personal preparation 💡
We often blame burnout on companies, bosses, or clients. Sometimes that is true. Often it is poor self-management. If the body is under-recovered, the mind cannot do elite work.
↳ Sleep: a consistent window on the calendar, not a wish.
↳ Fuel: protein, water, and planned meals that keep energy stable.
↳ Training: short, regular sessions that build capacity.
↳ Focus: time-blocked deep work, notifications off, phone out of reach.
↳ Boundaries: say no to protect yes.

The professional who treats recovery like a deliverable shows up sharper, decides faster, and needs fewer meetings. Preparation compounds because errors do not.

Winning arrives when preparation removes luck from ordinary days. Munger’s point is simple. The outcome you want is controlled by the inputs you control.

Three moves to start today:
✅ Pick one recurring process and write the one-page SOP. Ship it by end of day.
✅ Replace your longest weekly meeting with a memo, a clear decision, and a 30-minute cap.
✅ Schedule your personal prep: sleep window, two workouts, and three planned meals.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

MICROMANAGEMENT IS QUIET. 


When leaders hover, teams slow down, hide risk, and stop thinking. The helicopter feels helpful in the moment. Over time it kills judgment, speed, and trust.

Here is the operating view of micromanagement and what to do instead. 💡

What micromanagement really signals
↳ Unclear outcomes. People can’t hit a target that keeps moving.
↳ Low trust in skill or system. Leaders try to control every turn of the wrench.
↳ Fragile execution. Work depends on one person’s constant check-ins.
↳ Missing visibility. Leaders hover because they can’t see the work in a clean way.

Cost to the business
↳ Latency everywhere. Reviews stack up, decisions wait, momentum dies.
↳ Talent atrophies. The best people disconnect or leave.
↳ Risk hides. Teams optimize for looking safe, not being honest.
↳ Capacity shrinks. Managers spend time supervising tasks, not improving systems.

Replace the helicopter with a system that scales thinking:

1️⃣ Define outcomes, not tasks
↳ Write the 1–3 measurable results for the week or sprint.
↳ Tie every task to a goal or KPI. If it does not connect, delete or park it.

2️⃣ Give decision rights in writing
↳ RACI is fine. Even better, a simple map: “Who decides, who contributes, who is informed.”
↳ Pre-authorize thresholds. “If impact is under $X or risk is low, ship without me.”

3️⃣ Run a visible operating cadence
↳ Daily 10-minute standup for blockers, not status theater.
↳ Weekly 30-minute outcomes review. What shipped, what slipped, why.
↳ Monthly retro. Keep, stop, start. One improvement locked each month.

4️⃣ Build information radiators instead of status meetings
↳ One-screen dashboards for flow, quality, and risk.
↳ Kanban board with owners and due dates.
↳ “Red means help.” Make raising your hand easy and fast.

5️⃣ Coach with questions, not keyboards
↳ “What options did you consider?”
↳ “What’s the smallest safe test you can run today?”
↳ “What would make this 2x faster with the same quality?”

6️⃣ Inspect at the right altitude
↳ Leaders review outcomes, exceptions, and learning.
↳ Managers review plans, risks, and capacity.
↳ Makers own execution details. That’s their craft.

7️⃣ Create safety for speed
↳ Pre-mortems for big bets.
↳ Checklists for repeatable work.
↳ Write the rollback plan before you ship.

If you must hover, hover over clarity. Then get out of the way. Your job is to design the game so skilled people can play it well, at pace, with pride.

Three moves you can run this week:
✅ Write decision rights for your top 3 workflows, including ship-without-me rules.
✅ Replace one status meeting with a live dashboard and a 10-minute blocker standup.
✅ Shift your next review from “edits” to “questions,” then approve a small, safe test.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

0 → 30,000 in 18 months 
What I wish I knew when I started. 

1️⃣ It’s a second job.
The hours surprised me, and they reshaped my mornings, evenings, and family rhythms. If I’d known the workload upfront, I probably wouldn’t have done the work, nor would my wife have signed-off. 

↳ Initial Cadence: 5–8am, 7–11pm (create + engage)
↳ Set expectations at home and plan capacity like client work
↳ Start small

2️⃣ Love the process or stop.
Sustaining daily work only happened because I came to love designing, writing, editing, and shipping.
↳ Rotate formats to keep energy high
↳ Keep it playful and iterative
↳ If creating doesn’t inspire you, try a different approach. 

3️⃣ Output compounds.
The early days felt invisible, 1 to 4 reactions, maybe one or two comments per post. Quantity became quality.
↳ Push publish, don’t let insecurity stop you
↳ Hundreds of thousands of words add up
↳ Expect months before lift, then momentum

4️⃣ Relationships are the ROI.
LinkedIn became a global room of peers, clients, and friends who sharpen my work, my life and my perspective. 
↳ Track intros and opportunities, 
not just followers
↳ Use comments to make new friends 
↳ Community > vanity metrics

5️⃣ Engagement is the engine.
Publishing is only half the game, showing up in others’ threads taught me what works and earned trust I couldn’t earn elsewhere. 
↳ Comment daily with substance
↳ Treat feeds as a content classroom
↳ Learn by observing what lands

6️⃣ Make feedback your fuel.
Fall in love with the daily feedback loop. 
↳ Crickets, low saves, few reposts = data
↳ Ask: hook fail, story weak, CTA unclear, format off?
↳ Log tests, tweak one variable, ship tomorrow

7️⃣ Build systems (then a team).
Consistency requires an operating system, not willpower. Systems lowered friction so my creativity could show up on time and on point.  
↳ Batch topics, scripts, and assets
↳ Template everything, keep an idea backlog
↳ As the brand becomes a business, hire help

8️⃣ Co-write with AI, don’t hide it.
Claude and ChatGPT became collaborators, not shortcuts. Prompt craft improved my thinking and made better drafts, faster.
↳ Feed context, tone, examples; demand outlines + rewrites
↳ Use AI for synthesis and structure, you add judgment and voice
↳ This isn’t cheating, it’s the logical, creative and only smart path forward

I also want to thank some of my incredible friends and teachers who have helped me along the way: 

Teachers: 
Chris Donnelly 
Josh Sanders 
Dora Vanourek 
Will McTighe 
Ashley Couto 
Ford Coleman  

Friends 
Elis Wilkins 
Ali Mamujee  
Jorge Luis Pando 
Cory Blumenfeld 
Mike Leber 
Marsden Kline 
Owain Lewis 
Dennis Berry  
Ryan Yockey 
Andrea Petrone  

There are so many more, but be sure to give all these incredible folks a follow. 
 
If you’re just starting on LinkedIn and would like some perspective, I’d be happy to help (scheduling 🔗 in the comments). 

♻️Repost & follow John Brewton for content that helps.

📬Subscribe to Operating by John Brewton

WINNING COMPANIES RUN ON A LOOP 🧠
Do -> Fail -> Learn -> Grow -> WIN. 🏆 

Do something new and hard.
Fail at something new and hard.
Learn from the new and the hard.
Grow from the new and the hard.
Win at the new and the hard.

Einstein called it success in progress, operators call it work in progress with purpose

Here is the loop for operators and leaders in any company.

1️⃣ DO NEW AND HARD
↳ Pick one constraint that blocks value, cycle time, cash, or quality.
↳ Write a one page brief, the why, the change, the test window, the owner.
↳ Time block deep work for you and the team, protect it.

2️⃣ FAIL NEW AND HARD
↳ Set safe to fail bounds, budget, time box, and a clear stop.
↳ Define success and failure in advance, the metric moves or it does not.
↳ Invite dissent early, gather three risks, run a premortem.

3️⃣ LEARN FROM NEW AND HARD
↳ Run a 20 minute AAR, what should happen, what happened, why, one change.
↳ Capture the numbers, lead time, error rate, cost per unit, customer impact.
↳ Log the lesson where work lives, ticket, SOP, Notion, wiki.

4️⃣ GROW WITH NEW AND HARD
↳ Standardize the win, update SOPs, checklists, and defaults.
↳ Train the team in five minutes, show the change, practice once, confirm.
↳ Automate or templatize, reduce touches, remove waits.

5️⃣ WIN AT NEW AND HARD
↳ Measure the before and after, publish the chart, close the loop.
↳ Celebrate the team, share credit, move on quickly.
↳ Roll learning to the next constraint, continue the loop.

This mindset is not motivational, it is mechanical. It keeps leaders out of opinion fights, it moves the company through focused experiments that compound. Small loops shipped weekly beat big bets shipped yearly. Operators who live this loop build moats, because the culture learns in public, corrects fast, and keeps standards rising.

💡 Practical signals you are on track
↳ Meetings get shorter because decisions arrive with data.
↳ Queues shrink because work enters ready and exits clean.
↳ Morale improves because people see progress and own it.

Three moves to make this week:
✅ Choose one hard problem tied to revenue, margin, or cycle time.
✅ Publish a two paragraph experiment brief, set guardrails, and schedule the review.
✅ Convert the learning into one change, update the SOP, train in five minutes.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Titles don’t define Elite Operators.
Their meticulously developed habits do. 

Day in and day out, they approach problems, people, and processes with a discipline that compounds into excellence.

Here are the 9 habits of elite operators:
↳ They simplify complexity into clarity.
Noise drowns teams. Clarity directs them.
↳ They focus on outcomes, not activities.
Effort doesn’t matter if it doesn’t produce results.
↳ They measure twice, execute once.
Preparation prevents rework. Speed without accuracy is wasted energy.
↳ They admit mistakes quickly, then fix them.
Ego slows progress. Honesty accelerates it.
↳ They balance speed with precision.

Not everything needs to be perfect, but nothing can be sloppy.

↳ They build systems that outlast them.
Great operators don’t just solve today’s problems, they prevent tomorrow’s.
↳ They see risk as data, not fear.
Information fuels action. Fear paralyzes it.
↳ They connect daily work to the mission.
Without purpose, tasks lose meaning. With it, they drive momentum.
↳ They leave things better than they found them.

Excellence is compounding improvement, not one-time heroics.

Elite operators know the game isn’t about being everywhere or doing everything.

It’s about building habits that consistently align effort with impact.

If you want to operate at the highest level, ask yourself daily:
Am I simplifying or complicating?
Am I chasing activities or driving outcomes?
Am I leaving things better than I found them?

Start here: 
✅ Build clarity into every decision
✅ Replace ego with honesty and speed
✅ Focus on impact, not effort

Do this long enough, and you’ll separate yourself from 90% of operators.

🟧 Do. Fail. Learn. Grow. Win. 
🟧 Repeat. Forever.

♻️ Repost & follow John Brewton for content that helps.

📬 Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗 in profile).

Curiosity is the operator’s advantage. 
Curiosity is a requirement for success. 

I’m a big Marc Andreessen fan and sincerely appreciate this excerpt from a blog post he wrote in 2007. 

The people who build durable, important companies are not nudged by deadlines. They are pulled by the work. They ask simple questions, test in small loops, and keep going until the mechanism is clear. It is not showy. It is steady, patient, and often hard. But it moves the numbers because it moves the system.

I believe in working very hard at your craft. Reading the docs. Tracing the workflows. Sitting with the team on the floor. Shipping the fix. Doing it again tomorrow. 

That level of effort is how defects fall, cycle time shortens, and customers feel the difference. 

Margins expand when problems are solved at the root and new value replaces waste.

I feel fortunate that my path led first to economics, then to studying, and learning through practice, how companies actually operate. 

That work still interests me every day. I like learning why a process works, how to improve it, and what history can teach about the next step. I try to carry that curiosity into everything I build and share.

Our work should be demanding. It should ask for focus when we are tired and another revision when “good enough” is easy. But it is worth it. 

Better companies serve customers better. Teams grow. Careers compound. You do not need to be the loudest voice. You need to be the one who cares enough to understand and fix what matters.

If you want an edge, love the craft enough to become excellent at it. Put your name on the result and let the customer decide.

Start here:
✅ Block 45 minutes each day to study one part of your system.
✅ Run one small test per week and write a 5-line readout.
✅ Ship one customer-visible improvement every Friday.

How do you feel? 

What do you do? 

What am I missing that would make this better? 

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

graphical user interface, text, application

Your edge is not brilliance. Your edge is eliminating preventable mistakes at scale.

“Stupid” is not about IQ. It is the predictable way normal people, in normal systems, create avoidable loss. Fatigue, incentives, unclear ownership, missing guardrails. These are magnets for unforced errors. They compound faster than strategy.

Here is where “stupid” hides in plain sight:

↳ Unowned outcomes. Many helpers. No single DRI.
↳ Fancy dashboards. Wrong definitions. Bad decisions.
↳ Projects with no kill switches or stage gates.
↳ Shipping on Fridays. Hope as the rollback plan.
↳ Finance leaks under 1 percent. No one’s job to plug them.
↳ Naming chaos. Files, SKUs, customers, environments labeled five ways.
↳ Meetings that decide nothing. Decisions that meet no one.
↳ Permissions set “for now,” kept forever.
↳ Senior leaders skipping checklists because “we’re busy.”
↳ Hiring fast. Onboarding slow. Then blaming talent.
↳ Two people own the process. So no one actually owns it.
↳ Over-automating brittle steps. Under-documenting resilient ones.
↳ Tribal knowledge that lives in DMs and memories.
↳ “Temporary” reports that drive permanent forecasts.
↳ Shadow pricing, shadow inventory, shadow scope.

Antidotes are boring by design:

↳ Write the one-sentence outcome for every project.
↳ One DRI per outcome. Helpers documented by name.
↳ Define every metric in a living glossary. Freeze definitions during a cycle.
↳ Two-way doors decide fast. One-way doors slow down on purpose.
↳ Pre-mortems before big launches. Post-mortems within 48 hours.
↳ Checklists for critical paths. Leaders use them first.
↳ Label everything. Version everything. Archive nothing without intent.
↳ Create “tired person tests.” Could a new hire break this in three clicks?
↳ Weekly leak hunt: refunds, chargebacks, write-offs, shrink, rework.
↳ Meeting contracts: purpose, prep, owner, decision rule, timebox.
↳ Public runbooks. Short. Plain language. Screenshots beat prose.
↳ Default off for prod access. Default on for logging.
↳ Stop Friday releases unless you’ve rehearsed the rollback.
↳ Celebrate deletion. Old reports, stale automations, dead processes.

The lesson is simple. Strategy multiplies only after stupidity divides. If you reduce unforced errors, your “average” team will look elite.

Three moves you can make today:

✅ Write the DRI and one-sentence outcome for your top project.
✅ Run a 30-minute leak hunt. Close one hole before lunch.
✅ Pick one ritual to standardize with a checklist. Use it this week.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

“Spend zero time on what you could have done, and devote all of your time on what you might do.” — Ben Horowitz

Operators win by shortening the distance between “uh-oh” and “back to stable.” Not with heroics, with systems.

🧠 From mantra to mechanism
↳ Triage Clock: 30 minutes max to (1) name the issue in one sentence, (2) assign one owner, (3) pick one channel, (4) publish the next update time.

↳ Reversible-by-Default: If the fix is cheap to undo, the doer decides. Escalate only when the change is hard to reverse.

↳ Contain → Correct: First shrink the blast radius, then ship the smallest fix that reduces risk in the next hour.

↳ Observe Window: 15 minutes of live data before the next move. If risk rises, revert. If risk falls, expand.

↳ Write-as-You-Work: Timestamp actions. Capture the one-line rule you’d teach a new hire. Update the runbook before you close the loop.

↳ Blameless, Brief Review: 10 minutes, three bullets—Trigger, Response, Guardrail—then turn the guardrail into an alert, automation, or checklist.

💡 Metrics that drive behavior
↳ TTS (median & P90)
↳ % incidents resolved within SLA
↳ % reversible actions taken without approval
↳ Incidents → Guardrails ratio (are we getting safer every week?)

Common drag? Post-mortem debates while customers wait. Build an outcomes over autopsies mindset to get the problem immediately solved. Fast learning, faster execution. 

Start Here:
✅ Define and publish your 30-minute Triage Clock.
✅ Ship a 3×3 reversible-decision matrix and pre-authorize it.
✅ Stand up a simple TTS dashboard your team sees daily.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Time to Stable Beats Time to Perfect in Operations

High-output teams are built by high-output leaders that build HIGH-OUTPUT WEEKS.

High-output weeks aren’t about squeezing more hours. They’re about installing a simple operating system that converts attention into outcomes. Here’s the framework my carousel points to—and why it compounds for operators. 

💡 The core idea
Your calendar is not a diary, it’s the OS for your company brain. When time has purpose, work has direction. The carousel shows the pieces, but the architecture is what matters:
↳ Rhythm: Give every day a job so priorities have a home.
↳ Artifacts: Define and ship tangible outputs daily so progress is visible.
↳ Guardrails: Contain meetings, protect focus, and make mornings sacred.
↳ Decision Flow: Move choices from document to done with owners and deadlines.
↳ Scoreboard: Measure time like money to reveal bottlenecks and improve.

🧠 Why this works for operators
Operators carry the burden of context switching, escalations, and decisions. Without a weekly architecture, you and your team become reactive: 
↳ Cycle times shrink because deep work happens in protected blocks.
↳ Throughput rises because every day produces an artifact, not just activity.
↳ Quality improves because decisions are owned, dated, and reviewed.
↳ Revenue moves because pipeline gets a dedicated day and attention.
↳ Team trust grows because 1:1s and weekly leadership are structured and predictable.

What changes first? Language. When your calendar encodes strategy, you talk in outcomes, not tasks: 

🟧 “Ship spec by 4:30,” 
🟩 “Unblock Deal #3,” “
🟧 Approve budget move,” 
🟩 “Close the loop Friday.” 

That clarity reduces friction, invites accountability, and makes coaching concrete. Over a month, this becomes cultural: fewer ad-hoc pings, faster decisions, better demos, steadier cash.

💡 How to think about meetings
Only five types exist (decision, design, 1:1, review, retro). Everything else is noise. If it doesn’t have an owner, purpose, and expected outcome, it doesn’t go on the calendar. That’s how leaders earn back maker hours without sacrificing alignment.

🧠 The payoff
A high-output week is the smallest unit of a high-output company. Nail the week, and the quarter handles itself: cleaner metrics Monday, revenue momentum Tuesday, product velocity Wednesday, system strength Thursday, financial clarity Friday. Repeat that rhythm and you compound.

3️⃣ Moves to Start Today
✅ Block two maker windows on your calendar and auto-decline outside them.
✅ Name one artifact you will ship before 4:30 and post it to your team channel.
✅ Pick a decision you’ve been circling—assign an owner and a deadline now.

♻️Repost & follow John Brewton for content that helps.

🟥  Do. Fail. Learn. Grow. Win.
🟥  Repeat. Forever.
____
📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile). Paid subscribers get weekly execution playbooks, private AMAs, and templates that turn strategy into shipped work.

Operating Productivity: Build A High-Output Week

Great operators do not just move fast. 
They know when to wait, and why. 

Patience is not passive. It is a system for compounding advantage while rivals burn out. That is the core idea in today’s carousel. 

↳ The reality gap, page 2: leaders praise speed to market, yet durable innovations often take years. Winners plan for slow build, fast finish.

↳ The patience premium, pages 3 and 7: great work and great companies accrue value over long horizons. Four years on a ceiling, six on a novel, nine to pivot a model, then outsized returns show up.

↳ The quitting curve, page 4: most give up at plateaus and inflection points. Operators who stay through the ugly middle harvest the upside the quitters leave behind.

↳ The patience matrix, page 5: urgency without patience is stress, patience without urgency is drift. High urgency with high patience is the mastery zone.

↳ The 3-2-1 progress method, page 6: when momentum feels invisible, count small wins, track skills, and anchor on one long metric that matters. This protects morale and creates proof of progress.

↳ Strategic impatience, page 9: accelerate learning cycles and feedback loops. Be impatient with discovery and correction, patient with outcomes.

↳ The daily patience system, page 10: blend iterative work with foundational work, validate on a cadence, and ask the three-year test for decisions. This is how patience becomes an operating rhythm.

↳ Compound value math, page 11: one percent better daily, forty-plus focused hours a year from minutes a day, elite outcomes in three years. Consistency beats intensity.

↳ The invisible edge, page 12: document struggles, celebrate small wins, measure lead indicators. These make persistence practical.

The point is simple. Patience is a design choice. It is a portfolio of cycles, reviews, and rules that defend focus, reduce variance, and let compounding do its job. You build this into the calendar, the metrics, and the culture. When markets wobble, your system holds the line. When the window opens, you have the skill, the proof, and the stamina to move.

🧠 Operating takeaway: Speed is a tactic. Patience is a strategy.

💡 Ask yourself: Where am I mistaking motion for momentum, and how can I install systems that compound quietly for 12 to 36 months?

Start here:
✅ Define one lagging outcome that really matters, then three leading behaviors you will measure weekly.
✅ Schedule a 14-day validation loop, and make a visible record of small wins.
✅ Protect 30 percent of your time for foundational work that will not pay off this quarter but will change your next three years.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

The Operating Power of Patience

🧠 The Quitting Curve: Why most operators tap out right before it gets good, and why patient execution needs to be a virtue of your company. 

MIT Sloan research on learning and persistence shows a simple pattern: effort compounds late. The work feels hardest right before results inflect, so most people quit at the exact moment they’re closest to breakthrough. 

Here’s the operating reality behind the slide:
1️⃣ Year 1 — Foundation (90% still in)
You’re laying pipes, not pouring champagne. Systems are crude, handoffs messy, metrics wobbly. Your job: build the machine that builds the product.
2️⃣ Year 2 — Plateau (60% remain)
The novelty is gone. Process debt surfaces. Stakeholders get impatient. This is where discipline beats enthusiasm.
3️⃣ Year 3 — Inflection (40% remain)
Inputs stabilize, feedback loops tighten, small compounding advantages show up. Most exits happen here because gains feel slow and the grind is visible.
5️⃣ Year 5+ — Acceleration (12% remain)
Mastery looks like “boring excellence”: predictable throughput, fewer meetings, decisions that land earlier with less drama. Margins expand because variance shrinks.

What to do with this as a founder/operator:
↳ Treat plateaus as a phase, not a verdict. Plan for them in your model and calendar.
↳ Replace “motivation” with cadence. Ship on a weekly beat, review on a monthly beat, reset on a quarterly beat.
↳ Measure learning speed, not just output. Time-to-insight is the leading indicator for time-to-profit.

How to keep going when it’s tempting to stop:
↳ Pre-commit to a 24-month operating cadence before you see results.
↳ Make quitting expensive: public goals, weekly demos, investor/mentor reviews.
↳ Keep a rolling 12-week scoreboard. Highlight learning velocity, not just wins.
The curve punishes impatience and rewards consistency. Stay long enough for compounding to show up.

Start here: 
✅ Pick one workflow and cut its cycle time by 25% in 30 days.
✅ Publish a one-page decision charter and enforce it for 90 days.
✅ Ship a weekly review memo (same template, every week) for the next 12 weeks.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Sometimes the hard thing is the decision to move forward and stop looking back. 

Operators, this is our job description. When a problem hits, the company needs speed, not a seminar on blame. Learn what failed in minutes, then redirect all attention to the next right move. The metric is time-to-stable, not time-to-perfect.

🧠 Operating stance: outcomes over autopsies.
💡 Fast learning, faster execution.

Here is a practical pattern I use when an issue presents itself:

1️⃣ Orient in minutes
↳ Name the problem in one sentence.
↳ Assign one accountable owner, declare a clear stop time for triage.
↳ Select a single channel for updates so people are not chasing pings.

2️⃣ Contain, then correct
↳ Reduce blast radius first: pause the job, roll back, or put in a manual workaround.
↳ Decide on the smallest reversible fix, ship it, watch real data for 15 minutes.
↳ If risk is rising, revert. If risk is falling, expand carefully.

3️⃣ Decide with lightweight heuristics
↳ “What is the next action that shrinks risk the most in the next hour?”
↳ “What can we test by end of day that teaches us the most?”
↳ “What is good-enough to restore service and trust now?”

4️⃣ Write as you work
↳ Log the timestamped actions and observations.
↳ Update the runbook while the facts are fresh, not tomorrow.
↳ Capture a one-line rule you would teach a new hire.

5️⃣ Post-fix review that is brief and blameless
↳ 10 minutes, three bullets: trigger, response, guardrail.
↳ Turn the guardrail into automation, alerting, or a checklist.

Common drags that kill velocity:

↳ Debating counterfactuals no customer will ever see.
↳ Perfect root-cause research before service is restored.
↳ Too many approvers for a reversible action.
↳ Starting new threads instead of closing the loop in one.

Your edge is cycle time. Shrink the loop from problem to learning to fix. When you model this bias for action, your team learns that progress beats posturing, and that lessons are for tomorrow’s excellence, not today’s delay.

✅ Set a 30-minute triage rule for every critical workflow.
✅ Define “reversible by default” decisions and preauthorize them.
✅ Add a one-page decision log to every incident to convert action into learning.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

STOP OVERTHINKING. 
START DOING.

Overthinking is a quiet tax on momentum. Founders, strategists, and executives often search for perfect answers in documents and meetings. Most answers live in the work, in the conversations with customers and teammates, and in the next version of the product.

Action creates signal. Signal guides strategy.

Here is a simple operator’s loop to find the truth faster: 

↳ Work: Build a thin slice, not a grand plan. Ship a rough version that exercises the core system.
↳ Listen: Sit with the user, the rep, the tech, the finance lead. Ask what slowed them down, what broke, what they did to get around it.
↳ Decide: Use small bets. Timebox decisions. Escalate only the choices that move cash, risk, or the roadmap.
↳ Improve: Tie next work to the top friction you just heard. Document the change, teach it once, then automate it.

The work reveals constraints, 
costs, and customer reality.

Practical rules that keep you out of analysis paralysis:

↳ Choose the next reversible step, then set a 48-hour review.
↳ Define what good looks like in one paragraph, not a deck.
↳ Keep decision logs. What we decided, why, owner, revisit date.
↳ Instrument the process. If it cannot be measured, it cannot be managed.
↳ Hold listening hours every week, 30 minutes with front line voices.
↳ Replace status theater with a one-screen dashboard that tracks flow, quality, and cash.
↳ Learn in public with your team. Share what failed, what you changed, and what you expect to see next.

The image says it well: start doing.
Working teaches what the model missed.
Listening surfaces the blind spots.
Building creates the only feedback that matters, market feedback.

When you run this loop, strategy gets sharper, hiring gets clearer, margins improve. You stop guessing about “what should work” and start managing what does.

Three constraints to protect speed and quality:

↳ Scope small, ship weekly.
↳ Surface friction, fix daily.
↳ Close the loop, teach and automate monthly.

Now, choose progress over perfection. Replace debate with data from real usage. Your team will follow clarity and pace.

Three actions for this week
✅ Book two listening sessions with people closest to the customer.
✅ Define a one-screen view of your product or process, owner included.
✅ Ship one reversible change, measure one outcome, write one paragraph of learning.

♻️Repost & follow John Brewton for content that helps.

✅ Do. Fail. Learn. Grow. Win.
✅ Repeat. Forever.

⸻

📬Subscribe to Operating by John Brewton for deep dives on the history and future of operating companies (🔗in profile).

Taplio

John Brewton's Linkedin Analytics

's Best Posts (last 30 days)

Want to drive more opportunities from LinkedIn?

Taplio

.css-1jgreyo{background-image:linear-gradient(284deg, rgba(39,43,72,1) 0%, rgba(33,47,183,1) 100%);color:transparent;-webkit-background-clip:text;background-clip:text;}John Brewton's Linkedin Analytics

's Best Posts .css-qqfgvy{font-size:var(--chakra-fontSizes-md);}(last 30 days)

Want to drive more opportunities from LinkedIn?

John Brewton's Linkedin Analytics

's Best Posts (last 30 days)