The hottest Operations Substack posts right now

And their main takeaways
Category
Top Business Topics
Sustainability by numbers • 246 implied HN points • 23 Mar 26
  1. AI plus satellite-based route planning can sharply cut contrail formation when crews follow the plan — flights that flew avoidance routes saw about a 63% reduction in contrails.
  2. The main barrier is human and operational: dispatchers chose the avoidance plan rarely and pilots only partly executed it, so overall contrail reductions were only around 12%.
  3. Scaling this up will require better tools (like vertical route profiles), automation or incentives to make avoidance routes the default, and regulatory or financial support; early data suggest little extra fuel burn but more study is needed.
OSS.fund Newsletter • 56 implied HN points • 26 Mar 26
  1. Buyers have shifted — they are more informed, hypothesis-driven, and expect fast, measurable results instead of broad discovery or generic workshops.
  2. AI-native competitors win by showing up narrow and pragmatic, offering tight scopes, quick proofs, and practical data-governance that remove friction.
  3. Traditional IT services can stay relevant by upgrading commercial skills with hands-on drills that turn messy account context into next steps, tighten proposals, handle governance, and prove value quickly.
TK News by Matt Taibbi • 4518 implied HN points • 06 Feb 26
  1. A regular segment was paused this week because the host was too sick to record, and it will return next week.
  2. The publication has been light on content lately, and changes meant to fix that will be implemented after the weekend with readers asked to check back Monday.
  3. An apology was offered for the interruption, and readers were wished a good weekend and reminded to tune in Monday morning.
Gad’s Newsletter • 26 implied HN points • 23 Mar 26
  1. UPS deliberately shrank its post‑pandemic network and cut low‑margin Amazon volume because the expanded capacity no longer matched demand and was destroying profits. The company is trading top‑line volume for a leaner operation to restore margins by closing buildings and cutting roles.
  2. Contraction is being paired with a big automation and technology bet — about $9 billion in robotics, RFID, and facility upgrades — to replace manual labor and rebuild a smaller, denser network around higher‑margin healthcare, SMB, and premium shipments. The goal is to raise revenue per piece and reduce labor intensity.
  3. Execution and timing are the key risks: union pushback, automation delays, and a leaner FedEx competing on price could undermine savings or leave the network underutilized. Getting closures, route consolidation, and automation sequenced correctly is essential to avoid degraded service or margin pressure.
Software Design: Tidy First? • 1811 implied HN points • 04 Feb 26
  1. Seeing AI’s value only as labor replacement is too narrow; AI also raises company value by increasing revenue, shifting timing of cash flows, and creating optional future paths.
  2. AI can boost revenue and growth by scaling human work, enabling personalization at scale, and adding new features customers will pay for, not just by cutting headcount.
  3. AI creates optionality and timing benefits—like deferred hiring or infrastructure, access to new markets and business models, and faster experimentation—that increase value beyond immediate cost savings.
Get a weekly roundup of the best Substack posts, by hacker news affinity:
The Beautiful Mess • 555 implied HN points • 04 Mar 26
  1. Keep consistency minimal and practical. Choose a few shared concepts, rituals, or templates that actually help people do their work, not broad vague pillars.
  2. Expect variation and avoid dogma. Ideas spread unpredictably, so let teams adapt frameworks to their context instead of forcing uniform implementations.
  3. Use consistency as a scaffold with an expiration. Introduce temporary rules to stabilize change but set a reassessment date, and prefer nudges like defaults, templates, and visibility over heavy mandates.
One Useful Thing • 2598 implied HN points • 27 Jan 26
  1. Agentic AI lets people build working prototypes and explore multiple startup ideas far faster and much cheaper than before, cutting months and big costs out of early-stage work.
  2. Decide when to delegate by weighing how long the task would take you, how likely the AI is to succeed, and how much time it takes to prompt and review outputs. Improving the AI's success probability or lowering review overhead makes delegation more worthwhile.
  3. Traditional management skills—clear goals, specific deliverables, limits of authority, and good feedback—are now the key to getting useful work from AI agents, and common documents like PRDs or orders make excellent prompts.
Tanay’s Newsletter • 113 implied HN points • 03 Mar 26
  1. AI erodes labor-based moats like switching costs, application-layer scale, and generic process advantages, making it cheaper and faster to build features, migrate systems, and iterate.
  2. Defensibility shifts to hard-to-reproduce assets: proprietary first-party data, real marketplace liquidity and reputation, regulatory or physical rails, and unique processes that rely on exclusive signals.
  3. Some powers strengthen or split — model and infrastructure scale plus institutional trust grow in importance, while marketing-driven consumer brand shortcuts weaken as agents can deeply evaluate options.
Tiny Empires • 36 implied HN points • 07 Mar 26
  1. Most business problems are visible frictions—old pricing, unused features, and clunky onboarding—and can be fixed in one focused day by looking for what you’ve been avoiding.
  2. Use a simple schedule: raise prices and fix billing, cut or stop maintaining low-value features, improve onboarding, then automate a recurring task to reclaim time and boost revenue.
  3. Protect your attention by writing down what you’re not going to do; small, focused fixes compound over weeks and months, though they won’t save a fundamentally broken business model.
Gad’s Newsletter • 41 implied HN points • 16 Mar 26
  1. Inflation alone doesn’t explain Dollar Tree’s gains — the $1.00→$1.25 price bump and COVID-driven demand were the real revenue engines, while a shift toward low-margin consumables has quietly eaten into gross margins.
  2. Scale helped procurement but hurt profits: SG&A rose with store count as revenue per store fell, and the $1.25 price point forces roughly 80 transactions per $100, creating a labor-heavy cost structure that undermines operating leverage.
  3. The company’s escape hatch is DT Plus! — higher price tiers can cut transaction intensity and improve margins, but the outcome depends on accelerating Plus! penetration, bending the SG&A ratio, and stabilizing revenue per store.
The Beautiful Mess • 476 implied HN points • 16 Feb 26
  1. Teams juggle work in three modes: strategic (intentionally keeping and pruning options), lazy (scattered, novelty-driven work without discipline), and survival (forced triage where dropping anything has immediate costs).
  2. Without clear pruning, learning, and prioritization, strategic juggling can drift into lazy juggling, and accumulated drift can suddenly collapse into hard-to-escape survival mode.
  3. Regularly diagnose where you are, choose constraints on purpose, create breathing room, and set clear criteria for focus so you can move back toward strategic, compounding work.
Points And Figures • 426 implied HN points • 12 Feb 26
  1. In the very early days founders handle finance with simple tools like QuickBooks and often hire fractional CFOs to standardize books rather than making a full-time hire.
  2. Startups should prioritize product, engineering, and sales to find product‑market fit because finance is rarely a growth engine in the early stages.
  3. Around $10M ARR you need an in‑house CFO to professionalize finance for fundraising or an IPO; seasoned CFOs bring networks and roadshow experience, and a self‑styled ā€˜CFO’ at Series A or earlier is a red flag.
The Beautiful Mess • 621 implied HN points • 03 Feb 26
  1. Leaders should know each team’s purpose, who they serve, recent releases, key metrics, and rough priorities, but you don’t need ledger‑level detail — broad estimates are enough.
  2. Standardize cross‑organizational communication like release calendars, deployment records, and analytics so partners can see what actually shipped, but teams don’t all have to use the same tracking tool unless a lot of work spans groups.
  3. Low trust drives micromanagement and rigid tracking that kills productivity, so let teams pick their tools and surface context with goals, value models, charters, and problem‑based roadmaps, using temporary common systems only while untangling heavy cross‑team work.
High Growth Engineer • 1164 implied HN points • 04 Jan 26
  1. Executives promote engineers who deliver clear business impact, not just technically elegant code.
  2. Finish work end-to-end: ship customer-ready products, build tools that speed the team, take on the operational "dirty work," and anticipate problems before they happen.
  3. Grow and lead others by mentoring, setting standards, and training teams — that influence gets noticed and accelerates promotion.
The Beautiful Mess • 766 implied HN points • 01 Jan 26
  1. Protect focus by carving out fixed capacity for prevention and high-impact work so urgent, low-value tasks don’t always dominate.
  2. Favor fast learning and minimal shipable experiments: define the smallest thing to test in weeks, pre-authorize follow-ups, and use forcing constraints to avoid over-polishing or paralysis.
  3. Make priorities real from the top: allow teams to drop lower work, measure hidden drag as cost-of-delay, maintain a visible pull queue of small, valuable tasks, and fund low-cost experiments for longer bets.
The Beautiful Mess • 1190 implied HN points • 07 Dec 25
  1. Labeling relationships in work systems helps clarify how things are connected. This understanding can improve strategy and execution in organizations.
  2. Different mental models for goals and initiatives impact how teams operate. Each model assumes different relationships, affecting overall effectiveness.
  3. Many companies still rely on simple hierarchies, but real work often functions as a complex network. Mapping out these relationships can lead to better insights.
The Beautiful Mess • 528 implied HN points • 16 Jan 26
  1. Break work into a small set (3–5) of clear but flexible lanes with a one- or two-line intent; make them stable enough to get a groove but easy to reshape or retire as reality changes.
  2. Put real ownership on each lane (one to three people) and run simple routines—copy lanes forward and review weekly or biweekly—to surface what moved, what stalled, and where to course-correct.
  3. Work small and think big: focus on near-term actions you can influence while keeping longer-term direction soft, and treat lanes as a collaborative, iterative learning practice rather than a rigid framework.
Gordian Knot News • 80 implied HN points • 27 Feb 26
  1. Watching a guided refueling visit shows the work is largely automated and done by a small, specialized team. Public access like this can demystify nuclear operations and build enthusiasm.
  2. The plant’s safety culture is strict, with many checkpoints, procedural rules, and sensitive radiation monitoring that can even detect natural background radon.
  3. Despite visible precautions, dense-packing of spent fuel pools concentrates many reactor fuel loads in one place, raising concern about the risks from a prolonged station blackout.
Respectful Leadership • 54 implied HN points • 21 Feb 26
  1. A lunchtime event on February 24 in NYC will bring people together to discuss how AI is changing business, with abundant healthy food and pizza provided.
  2. Speakers will share practical AI use cases like automating residential building permits and warn about legal pitfalls, including the risk of losing attorney-client privilege when using AI tools.
  3. Talks will also cover startup and agency strategy — who to hire early (X-shaped people), how to integrate outside agencies, and new go-to-market opportunities driven by AI.
The Beautiful Mess • 674 implied HN points • 28 Dec 25
  1. Leaders should set clear intent and stay close to frontline reality so judgment, not rigid targets, drives decisions. This keeps outcomes directional instead of turning objectives into unforgiving contracts.
  2. Tech companies often celebrate empowerment but fail to build the doctrine, rituals, and training needed to support judgment-based leadership, so autonomy becomes performative. Without those mechanisms, people manage optics instead of sharing real problems early.
  3. Visibility from senior leaders isn’t automatically micromanagement; it feels threatening when there’s no safe escalation, trust, or shared practices. If those conditions are established, direct updates enable more useful conversations and better real-time guidance.
The Data Ecosystem • 339 implied HN points • 04 Aug 24
  1. The People, Process, Technology framework helps organizations balance these three key areas but often misses the importance of data. Companies should not just focus on technology but also consider how people and processes interact.
  2. A new framework that includes data is called People, Process, Technology & Data. This approach shows how these four components work together, helping organizations make better decisions and manage change more effectively.
  3. Using structured questions and understanding the roles of each component can enhance planning and execution in businesses. It's essential to revisit these elements regularly to stay aligned with goals and adapt as needed.
The Beautiful Mess • 647 implied HN points • 09 Dec 25
  1. Product teams need fast, frontline customer feedback like a restaurant’s servers provide; without immediate signals from users, teams can’t detect and fix problems quickly.
  2. Being busy isn’t the same as being effective: lots of meetings and tasks can hide low-impact work, often caused by misaligned leadership incentives and menu creep.
  3. Real outcomes require clear strategy, upstream discovery, and tight cross-functional coordination across Sales, Customer Success, UX and Ops, not just a busy engineering ā€œkitchen.ā€
OSS.fund Newsletter • 56 implied HN points • 26 Feb 26
  1. AI won’t magically flip a bank’s spend from run to change because banks are tightly governed and face real costs like compliance, dual-run tax, and mandatory testing that prevent a quick switch. These constraints mean savings come slowly and require human-controlled policy and evidence gates.
  2. Treat modernization as a spectrum and manage it as a portfolio: Operate, Comply, Harden & Simplify, and Compete & Grow. Use a Good Bank/Bad Bank approach with a policy-driven bridge, deterministic routing, and continuous reconciliation so migrations are auditable, reversible, and lead to real decommissioning.
  3. Use AI as an assistant to cut toil, automate evidence, speed analysis, and help translate legacy code, but don’t give it authority to change policies or skip validation. Capture the realistic savings to fund simplification and growth, aiming for practical targets (for example ~50/50 over five years) rather than expecting an immediate 60/40 to 40/60 flip.
Creating Value from Nothing • 132 implied HN points • 22 Jan 26
  1. Own inbound sales end-to-end by building systems that route leads quickly and make signing up simple, so growth doesn’t stall.
  2. Solve root causes instead of surface symptoms by creating repeatable workflows, clear handoffs, and measurable definitions of ā€œgoodā€ so the team doesn't rely on heroics.
  3. A scrappy, cross-functional culture with a bias toward action and rituals that celebrate gritty execution helps teams move fast, learn from outcomes, and sustain improvements.
Math Meets Money • 139 implied HN points • 19 Aug 24
  1. Math Meets Money is a newsletter that helps scientists understand the business world using clear explanations. It's designed for those with scientific backgrounds who want to transition into business roles.
  2. The newsletter addresses common barriers scientists face when entering the business world. These include feeling over-qualified, under-qualified compared to others, and struggling with the specialized language of business.
  3. Readers can expect daily briefings on business terms and concepts, along with deeper dives into case studies and current events on weekends. This is all aimed at empowering scientists to innovate in industry.
next big thing • 48 implied HN points • 16 Feb 26
  1. Automating an entire company now feels realistic because modern agentic AI can run end-to-end workflows across functions without constant human involvement.
  2. Teams are already embedding AI agents to write and deploy code, run experiments, monitor training, handle sales outreach, and keep finance operations running, producing rapid productivity gains.
  3. As AI handles more grunt work, humans will shift to directing agents and making high-level judgments, so taste and decision-making become more valuable than ever.
Software Design: Tidy First? • 1745 implied HN points • 13 Aug 25
  1. In a system, the capacity of the output is limited by the narrowest part, or pipe, so expanding other parts won't help if that part doesn't change. It's important to identify and address this bottleneck to improve overall performance.
  2. As an executive, you have the unique ability to see the entire process and make decisions to improve it, unlike those focused on their own tasks. This broader perspective allows you to manage resources and workloads effectively.
  3. Creating pressure to increase productivity can have negative consequences, such as stress and burnout. It's better to find a balance that promotes a healthy work environment and supports productivity.
Tiny Empires • 98 implied HN points • 30 Jan 26
  1. Pick one clear big goal and use it as the filter for every task you consider.
  2. Each day choose exactly three meaningful tasks from your prioritized list and schedule them the night before or during a weekly planning session.
  3. Block out 1–3 hour calendar slots for those tasks, overestimate how long they’ll take, and treat them like real meetings to ensure focus and accountability.
Sex and the State • 15 implied HN points • 02 Mar 26
  1. Running multiple blogs doubles the setup and maintenance work and makes it harder for new readers to discover all your writing.
  2. People follow people more than topics, so keeping your work in one place helps readers connect with you across different subjects.
  3. You can’t please everyone, so it’s better to have a distinct voice that attracts devoted readers; only split into separate blogs if the audiences or goals are truly incompatible.
ASeq Newsletter • 21 implied HN points • 02 Mar 26
  1. Oxford released its full-year 2025 accounts, and they broadly match the results it showed at JPM.
  2. A new CEO for Oxford Nanopore has started.
  3. Oxford confirmed cancellation of P2S support and said the ElySION product is cancelled too; ElySION had been on the market for about a year.
Startup Business Tips šŸš€ • 34 implied HN points • 15 Feb 26
  1. Know exactly who to sell to — document a five‑point ICP and a list of disqualifiers (ANTI‑ICP) and enforce it so your pipeline stops getting noisy.
  2. Pick one clear positioning anchor (product category or use case) and make it consistent across homepage, LinkedIn, demos, and sales materials; pause weak channels and focus deeply on the strongest one.
  3. Tighten execution with simple processes and metrics — add source attribution, track lost reasons, set hard open/close deal criteria, review demo recordings, and actively use case studies and referrals.
OSS.fund Newsletter • 37 implied HN points • 19 Feb 26
  1. AI is likely to cut or compress coordination-heavy middle management jobs first, like meeting coordinators, status reporters, and standardised team leads.
  2. Managers who design systems, own outcomes, and handle ambiguity will become more valuable and are less likely to be replaced.
  3. Survival means automating coordination, owning a measurable outcome, becoming the control plane that sets policies and escalations, and moving closer to money or risk.
Boundless by Paul Millerd • 98 implied HN points • 12 Jan 26
  1. Don’t gamble on quick fixes, viral hacks, or pricey masterminds — those are the ā€œcasinoā€ tactics where the house usually wins. Focus on real business models and the trade-offs that make them sustainable.
  2. Building a profitable solo business takes time and clear choices, often years of work; prioritize frameworks, consistent long-form content, and relationship-driven sales instead of chasing follower counts.
  3. Operational thinking and repeatable rhythms matter: use frameworks and processes to run your business, and treat products (like books) as leverage that still require years of work and ongoing maintenance alongside active client work.
OSS.fund Newsletter • 94 implied HN points • 22 Jan 26
  1. What you call flexibility may be hiding operational debt: manual workarounds, spreadsheets, and institutional memory erode margins and create single points of failure.
  2. AI can encode client-specific rules and handle exceptions at scale, letting you deliver personalized experiences without increasing marginal human effort.
  3. Audit recent special deals, map their hidden workflows, and encode repeatable rules so agents handle predictable exceptions while humans focus only on true edge cases.
Fish Food for Thought • 83 implied HN points • 21 Jan 26
  1. Leadership can take two effective shapes: a V-formation with clear direction, roles, and efficiency, or a murmuration with decentralized, rule-based adaptability.
  2. The right pattern depends on the situation — use V-style structure when coordination and reliability matter, and murmuration-style autonomy when uncertainty, speed, and learning matter.
  3. Leaders make either pattern work by shaping conditions: rotate leadership, clarify purpose and constraints, build trust and feedback, and align incentives so the chosen pattern isn’t undermined.
The Beautiful Mess • 330 implied HN points • 12 Nov 25
  1. Using different lenses helps us see various sides of a problem in product work. Each lens gives us a unique perspective, so more than one is needed.
  2. Understanding customer journeys and personas can reveal different experiences for different groups. This helps in tailoring services or products more effectively.
  3. Team interactions and boundaries play a big role in how work gets done. Recognizing these can improve communication and efficiency across teams.
VERY GOOD PRODUCTIZED GUIDES • 179 implied HN points • 04 Jul 24
  1. Many business owners think their business can't run without them due to fear of losing quality. But with the right systems, it can thrive even in their absence.
  2. Bottlenecks come from controlling client communication and deliverables too tightly. Letting go and empowering others can free up time and improve efficiency.
  3. Creating clear processes and hiring help allows business owners to focus on growth. Shifting to scalable models can also help in generating consistent income.
Huddle Up • 61 implied HN points • 26 Jan 26
  1. The Savannah Bananas sold about 2.2 million tickets across 113 games. That likely generated roughly $75–80 million in ticket revenue, putting them on par with many MLB teams.
  2. Merchandise became a massive revenue stream, with 787,000 buyers purchasing nearly 2 million items and driving over $50 million in sales. That likely exceeds retail revenue for many MLB clubs.
  3. Big revenues hide big costs: high player salaries, 700+ employees, and large travel and production budgets make the operation resemble a touring show more than a single-stadium team. Those expenses complicate profit margins and any claim of a $1 billion valuation.
Gad’s Newsletter • 47 implied HN points • 02 Feb 26
  1. Startups need different people as they grow: bushwackers to invent in chaos, off-road drivers to stabilize and scale, and F1 drivers to optimize and run at high efficiency.
  2. The biggest scaling mistake is hiring the right people for the wrong stage — add structure at the right time and integrate new roles carefully so you don’t smother innovation or collapse under chaos.
  3. Even mature companies must preserve some exploratory teams and have leaders translate between archetypes so experimentation and process coexist and each group is rewarded appropriately.
Fish Food for Thought • 27 implied HN points • 11 Feb 26
  1. Systems produce the results they’re designed for; when outcomes repeat, it’s a feature of the system, not just a few bad actors. If you want different results, you must change the system.
  2. How a team is organized and how people communicate directly shape the products and processes they build. Siloed or misaligned structures create brittle, broken systems, while aligned, autonomous teams make scalable, resilient ones.
  3. Leadership’s real work is system design: set information flows, decision rights, and incentives so the system rewards the behaviors you want. Blame and training are cheap fixes—real change is slow and structural.