The hottest Organizational Design Substack posts right now

And their main takeaways
Category
Top Business Topics

TBM 411: Messy Docs As Helpful Pattern

The Beautiful Mess • 581 implied HN points • 17 Mar 26
đź’Ľ Business Organizational Design
  1. High-performing teams often rely on messy, freeform docs—copying notes, links, screenshots, checklists, and inline todos—to externalize working memory and capture evolving product work.
  2. Those documents only stay useful when they’re part of a repeated ritual: frequent integration, reflection, and habit keep the artifacts current; without that repetition they decay into relics or private knowledge.
  3. Organizations still need legibility, so the aim should be to design small, intentional interfaces—minimal shared routines, objects, or language—that translate messy local work into clear signals without forcing teams to stop working the way they do.

TBM 410: Dancing With Problems

The Beautiful Mess • 912 implied HN points • 11 Mar 26
đź’Ľ Business Organizational Design
  1. Vague problem statements like “make the app easier” don’t help — be specific about what’s broken, why it matters, and what outcomes you want so you can diagnose and measure impact.
  2. Look at problems from multiple levels — user behavior, surrounding context, incentives, and long‑term strategy — and move between those views to test assumptions and find the real crux.
  3. Don’t jump to simple fixes; investigate trade‑offs, who relies on the data, and how changes shift work downstream, and create shared understanding so the team can navigate complexity together.

TBM 406: Seeing Everything, Understanding Nothing (The Context Trap)

The Beautiful Mess • 1163 implied HN points • 13 Feb 26
đź’Ľ Business Organizational Design
  1. Understanding is produced through interactions, not by assembling static background information. Context emerges as people engage with each other, their bodies, tools, and environment.
  2. AI and context engineering often treat context as a package you can merge, which pushes work toward solitary recombination of information. That model mistakes more data for understanding and ignores how interaction shapes meaning.
  3. Leaders should act as interaction designers, shaping dialogue, scenarios, and feedback loops so intent becomes the context for action. They must also recognize some decisions can use documented context while others require real-time coordination and emergent sensemaking.

Remote Work's Impact on Productivity

Arpitrage • 1097 implied HN points • 14 Jan 26
đź’Ľ Business Organizational Design
  1. Remote work affects firms differently by age: it tends to boost productivity at young startups but reduce productivity at older, established firms. This means the average effect looks small but hides large differences across companies.
  2. Remote work removes geographic hiring frictions for startups, letting them recruit talent from many places, grow faster, and improve worker–firm matching. Those hiring and matching gains explain much of the productivity lift for startups.
  3. Big firms face coordination and retention challenges with remote work, which helps explain pushes to return to the office, while remote-first startups help spread innovation beyond major city hubs and increase business dynamism.

TBM 405: Hope, Context, and Control

The Beautiful Mess • 502 implied HN points • 07 Feb 26
đź•ą Technology Organizational Design
  1. Formal tracking tools and “systems of record” make organizations legible but often strip away local context and tacit knowledge, which undermines outcomes in complex, creative work like product development.
  2. Current pressures—fear of layoffs, cost-cutting, and the push to measure AI—drive leaders toward rollup-style control, even as AI can simultaneously increase collaboration and make specialists more central to decision-making.
  3. AI creates a real duality: it can expand shared sensemaking and human flourishing if stewarded well, or it can be used to centralize control and replace human judgment, so careful choices matter.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

#53 - Forward Deployed AI Engineers: Great Expectations?

OSS.fund Newsletter • 18 implied HN points • 19 Mar 26
đź’Ľ Business Organizational Design
  1. Forward Deployed Engineers can build and embed AI tools, but they alone can’t rewire how a company actually works; enterprise AI is mainly an organizational change problem, not just a deployment problem.
  2. Companies need an internal, load-bearing layer—functional leaders, process owners, risk, HR, finance and exec sponsors—to redesign workflows, decision rights, incentives and vendor boundaries for AI to stick.
  3. The real talent gap will be people who can translate AI capability into operating-model change under real constraints, and the biggest advantage will come from making governance and the organization ready for AI, not just adding models to workflows.

TBM 403: The Seduction (And Folly) Of Rollups, Points, and (Most) Time Tracking

The Beautiful Mess • 542 implied HN points • 27 Jan 26
đź’Ľ Business Organizational Design
  1. Rollups, story points, and detailed time tracking feel like neat accounting but are really proxies and guesses, and over-relying on them leads teams to game metrics or manage the proxy instead of the real work.
  2. Time allocation is not the same as capacity — capacity is emergent and built over time — so measurement approaches must match the nature of the system rather than forcing every team into a single rollup model.
  3. Focus on outcome-oriented, low-cost signals that support decisions (like releases, customer impact, dependencies, and flow metrics), connect work to goals when it makes sense, and use rough estimates instead of chasing false precision.

Why Do Research Institutes Look the Same?

Asimov Press • 535 implied HN points • 08 Jan 26
🔬 Science Organizational Design
  1. Many new research organizations end up resembling traditional universities or startups, because a few familiar institutional models dominate the space.
  2. Forces like researchers' fear of harming future academic careers, investor demands for market-fit and growth, and tax/legal categories push organizations to conform to existing forms.
  3. To create truly different institutions, funders and founders can experiment with new legal structures, hire people less bound to academic incentives, use patient philanthropy, or try time-limited and project-based models.

TBM 398: Micromanagement? Or Staying Close to Reality?

The Beautiful Mess • 674 implied HN points • 28 Dec 25
đź•ą Technology Organizational Design
  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.

TBM 400: Strategic Portfolio Management Meets Product-Centricity

The Beautiful Mess • 396 implied HN points • 09 Jan 26
đź•ą Technology Organizational Design
  1. Software products and teams aren’t like stocks — they’re tightly entangled, slow to change, and hard to reallocate without big, lasting consequences.
  2. Lean and centralized portfolio approaches can restore flow and stabilize teams, but they often still assume capacity and flow are more liquid and reversible than they really are.
  3. In product-led tech organizations, portfolio decisions naturally live with product leadership and require organizational design choices (team topology, hiring, platform investment) rather than just a separate PMO doing prioritization.

My Circus, My Monkeys

Polymathic Being • 42 implied HN points • 01 Mar 26
đź’Ľ Business Organizational Design
  1. Don’t pretend complex problems aren’t yours — when teams shove issues into the seams between programs those “monkeys” become integration failures, so take responsibility and act like the ringmaster for the system.
  2. Use systems thinking with a simple mantra: Yes, and… So — acknowledge the issue, step back to see physical, logical, and human impacts, then decide what to own and what to hand to the right person.
  3. Embrace chaos intentionally: use practices like chaos engineering to test for resilience, balance disciplined execution with flexible processes, and look for innovation hiding in the seams.

TBM 396: So You Want To Define “The Problem”?

The Beautiful Mess • 489 implied HN points • 18 Dec 25
đź’Ľ Business Organizational Design
  1. Don't hunt for a single, perfect problem statement. Use multiple layers to see the customer's story, other actors' views, and the wider system shaping behavior.
  2. Listen to how customers describe the issue and collect perspectives from everyone involved, while treating history and past attempts as useful data.
  3. Turn the integrated understanding into small, testable interventions your product can realistically influence, and be clear about what capabilities or constraints will expand or limit your impact.

Work: The Four Big Shifts.

The Future Does Not Fit In The Containers Of The Past • 84 implied HN points • 01 Feb 26
đź’Ľ Business Organizational Design
  1. Work is becoming uncoupled from full-time jobs — companies will use more project-based hiring, freelancers, fractional roles, and AI agents to get work done.
  2. The future workforce will be a blend of humans and AI agents, with many people working fractional hours or as contractors, which changes benefits, hiring, and how work is managed.
  3. Leadership and organizations must reinvent: leaders need to learn and unlearn quickly and shift from control to influence. Companies should go AI-first, hire talent from anywhere, and become smaller, more agile, and distributed.

I wrote a book. Here’s why.

Anima Mundi • 123 implied HN points • 20 Jan 26
🪑 Design Organizational Design
  1. Don’t try to patch old systems; replace them by building new institutions designed to adapt and operate in parallel with the old ones so real change can take hold.
  2. Treat institutions as adaptive systems that must sense, decide, and act, and use concrete design patterns like bounded authority plus short implementation playbooks to build real adaptive capacity.
  3. Focus on action: target builders who will construct and scale these institutions and give them practical toolkits, workshops, and machine‑readable frameworks so they can implement the ideas.

8 Forecasts & Implications for the Years Ahead :: 2024+

Implications, by Scott Belsky • 1356 implied HN points • 04 Jan 24
đź•ą Technology Organizational Design
  1. The future will be personalized to your preferences, with digital experiences tailored to you.
  2. Local OS-native AI models will improve everyday life and redefine consumer AI, focusing on personalization, trust, and privacy.
  3. Small brands will become more competitive with big brands, AI will influence purchase decisions, and education will undergo a significant transformation.

#45 - Thought Experiment - Your "flexible" is hiding operational debt

OSS.fund Newsletter • 94 implied HN points • 22 Jan 26
đź’Ľ Business Organizational Design
  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.

Perfectly Designed for These Results

Fish Food for Thought • 27 implied HN points • 11 Feb 26
đź’Ľ Business Organizational Design
  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.

Agency motivates more than perks

A Bit Gamey • 33 implied HN points • 08 Feb 26
đź’Ľ Business Organizational Design
  1. People are motivated more by trust, autonomy and ownership than by perks; give clear responsibility and freedom and they will invest effort and care.
  2. Heavy rules, measurement and presence-for-presence policies push people toward safe, explainable work and kill initiative. Visibility and checklists can look like control but often reduce real progress.
  3. Design for agency by pairing clear outcomes and context with freedom in method; boundaries, not micro‑rules, keep teams creative and resilient—especially as AI takes on rule-following.

One list to rule them all

The Engineering Manager • 23 implied HN points • 13 Feb 26
đź’Ľ Business Organizational Design
  1. A single, stack-ranked list of priorities forces real focus and makes trade-offs visible, so you stop pretending everything is equally important.
  2. Multiple roadmaps and competing P0s create silos, spread engineers thin, and cause decision fatigue, which leaves work perpetually unfinished.
  3. Make a list of every initiative, force a strict one-to-n ranking with no ties, and use that list to guide staffing and the hard conversations about what to stop.

TBM 336: Product OS Design Tips and Principles

The Beautiful Mess • 1414 implied HN points • 26 Jan 25
đź’Ľ Business Organizational Design
  1. Think of your product operating system like a product itself. It needs to fit everyone's needs and constantly adapt to new challenges.
  2. Senior leaders should take responsibility for the product operating system. Their commitment is crucial to build trust and ensure everyone follows the guidelines.
  3. Start with simple interactions and routines for teams to use regularly. Well-designed rituals help improve communication and decision-making while reducing bureaucracy.

Why brand comes first

The Sociology of Business • 657 implied HN points • 29 Jan 24
đź’Ľ Business Organizational Design
  1. Short-term thinking in brand-building focuses on quick sales, leading to discount-dependency, while long-term prioritizes full-funnel strategy and brand desirability.
  2. Brand strategy goes beyond marketing, involving product design, retail, and cultural influence for modern retail success.
  3. Brand management emphasizes organizational cooperation, cultural awareness, and coordination across departments to renew brand perception and maintain relevance.

Improving Servant Leadership

Polymathic Being • 47 implied HN points • 18 Jan 26
đź’Ľ Business Organizational Design
  1. Good leadership already includes both service and direction, so carving out a separate "servant" category is unnecessary and can encourage people to skip core leadership duties.
  2. Overemphasizing the "servant" label often produces passive-aggressive leaders who avoid giving direction, confronting problems, or taking responsibility, which creates confusion, delays, and erodes trust.
  3. The remedy is to simply be a balanced leader: serve your team while also setting direction, enforcing standards, making hard calls, and adapting your approach to context.

The BBN Fund

FreakTakes • 37 implied HN points • 16 Jan 26
đź•ą Technology Organizational Design
  1. BBNs are small, engineering-first research organizations that pursue big, multidisciplinary technical goals by funding work with a mix of customer contracts and grants instead of typical VC or academic models.
  2. Pilot funding has shown there is both demand from flexible funders and supply of founders for BBNs, with early BBNs already winning substantial support and proving the model viable.
  3. The BBN Fund will seed and scale BBNs by deploying low-interest revolving loans, revenue-sharing investments, and modest undirected R&D grants, while a small Central Office will build pipelines of funders, customers, mentors, and contractors to make BBNs sustainable and investable.

Collapsing the Talent Stack, Persona-Led Growth & Designing Organizations for the Future

Implications, by Scott Belsky • 845 implied HN points • 06 Jul 23
đź’Ľ Business Organizational Design
  1. Edition #8 of Implications covers topics like restructuring teams, leveraging AI and collapsing talent stacks.
  2. In the age of AI, organizations need to focus on refactoring functions, embracing new technology like Generative AI, and understanding the impact on jobs.
  3. Persona-led growth emphasizes the importance of personal branding, user experience design, and the implications of company personification.

The Machine as Manager

Brave New Teams • 16 implied HN points • 01 Feb 26
đź’Ľ Business Organizational Design
  1. Autonomous organisations are already emerging: software now runs pricing, routing, risk and learning, while humans shift toward exception handling, goal-setting and oversight.
  2. Success depends on trust and accountability, not just accuracy; firms will need constraint-by-design, audit trails, incident reporting and clear governance to make autonomy legitimate.
  3. Autonomy brings real risks like metric gaming, slow drift and brittleness, so resilience measures and human custodians who set values and handle ambiguity are essential, and law and norms will likely evolve to reshape corporate forms and roles.

When Change Outruns Us

Fish Food for Thought • 42 implied HN points • 24 Dec 25
đź’Ľ Business Organizational Design
  1. When companies change faster than people can adapt, employees get exhausted and stop learning. That creates compliance without conviction and a culture that frays.
  2. Growth needs time to absorb change—quiet intervals for people to make sense, rebuild habits, and consolidate learning. Slack and recovery are not inefficiencies but necessary infrastructure for durable capability.
  3. Leaders should value direction and readiness over raw speed and watch for signs of saturation, slowing the tempo to let changes take root. Measure progress by clarity and strengthened capabilities, not by how many initiatives are launched.

Effectiveness is Signal minus Noise

A Bit Gamey • 20 implied HN points • 11 Jan 26
đź’Ľ Business Organizational Design
  1. Effectiveness comes from identifying the few things that truly matter and subtracting everything that interferes with them.
  2. Noise is socially acceptable — it feels like progress because it produces meetings, frameworks and consensus, but it quietly drains momentum and attention.
  3. Real focus means saying no and cancelling projects even when it’s uncomfortable; ask what the signal is, what’s interfering, and what would happen if you removed that interference.

TBM 269: Three Organizational Design Principles

The Beautiful Mess • 1057 implied HN points • 27 Jan 24
đź’Ľ Business Organizational Design
  1. Hierarchical Collaboration Parity is crucial for success in organizations - leaders need to collaborate as much as front-line team members.
  2. Alignment and Work Style Gaps need to be addressed to improve team effectiveness.
  3. Organizations must confront deep-seated tensions, or 'Elephants in the Room', to prevent adverse outcomes and stress on teams.

⤴⤵ Up Wing/Down Wing #29

Faster, Please! • 365 implied HN points • 21 Dec 24
đź•ą Technology Organizational Design
  1. OpenAI has introduced a new AI called o3, which is really good at solving math and science problems. It even did better than its previous version in many tasks.
  2. Companies will start changing how they work by using AI more in their structure. This can help teams work better together and boost productivity in the workplace.
  3. AI is becoming an important part of how organizations will operate in the future. Successful companies will mix human skills with AI to improve their processes and create more value.

DevProd headcount benchmarks, Q1 2026

Engineering Enablement • 10 implied HN points • 07 Jan 26
đź•ą Technology Organizational Design
  1. Most companies dedicate about 2–6% of engineering headcount to centralized developer productivity, averaging roughly 4.7%, and that percentage tends to shrink as organizations grow past ~1,000 engineers because tooling, automation, and leverage reduce headcount needs.
  2. The benchmark counts only narrowly-defined DevProd teams (internal developer platforms, DevEx/Productivity, build & release, test infra, and developer education/support) and excludes SRE, general cloud, security, and product-facing platform teams.
  3. Treat these numbers as a guideline, not a quota: use them to set initial headcount for a center of excellence and pair them with measurement (for example, the Core 4) to confirm the team is actually reducing developer friction.

Managing for Abundance, not Scarcity

Anant’s Newsletter • 8 implied HN points • 14 Jan 26
đź•ą Technology Organizational Design
  1. Writing code is now cheap because of AI, so the real constraints are context, taste, and decision-making — shift from protecting developer hours to enabling rapid experimentation and customer outcomes.
  2. Middle managers and leaders need to get hands-on and write code; pure people managers should no longer be acceptable, and everyone should be expected to be a builder.
  3. Restructure teams toward a 'diamond' model with more senior builders who can wield AI end-to-end, kill spec-first culture in favor of working prototypes, and measure success by iterations and customer outcomes instead of time estimates.

The age of the human bottleneck is ending. The age of human intent is beginning

Brick by Brick • 18 implied HN points • 27 Nov 25
đź•ą Technology Organizational Design
  1. AI will replace the old human-centric development pipeline with compact "Engine Room" teams where autonomous agents build, test, and deploy most of the product.
  2. This makes companies far more productive and lean — much higher revenue per employee, much faster shipping cycles, and many startups intentionally capping headcount because they simply don’t need more people.
  3. Human roles will shift from writing code to defining strategic intent, tuning and auditing AI systems, and handling judgment, ethics, and risk.

Rethinking organisation technology

The Uncertainty Mindset (soon to become tbd) • 119 implied HN points • 18 Oct 23
đź’Ľ Business Organizational Design
  1. Conventional hiring methods lead to rigid organizations. Instead, using open-ended roles helps companies adapt better to uncertainty.
  2. Open-ended roles allow employees to shift responsibilities and roles over time. This flexibility helps organizations respond quickly to changing situations.
  3. Organizations need to adopt different strategies for addressing true uncertainty, rather than just managing risk. This means being more open and adaptable from the start.

Organizational technology for uncertainty work

The Uncertainty Mindset (soon to become tbd) • 119 implied HN points • 06 Oct 23
đź’Ľ Business Organizational Design
  1. Uncertainty work is different from risk work. While risk work involves clear outcomes and known probabilities, uncertainty work deals with unknowns and needs flexible strategies.
  2. Everyday organizational processes shape how companies function. If these processes are based on outdated best practices that assume stability, they can hinder the ability to handle uncertainty.
  3. To succeed in uncertainty work, organizations must redesign their processes for hiring, goal-setting, and motivation. This means being open to change and creating conditions that encourage learning and adaptation.

The Missing Multiplier

Perspective Agents • 3 implied HN points • 22 Jan 26
đź’Ľ Business Organizational Design
  1. Top leaders now treat AI as the most consequential global issue, and leading AI builders warn of rapid advances that could replace many entry‑level white‑collar jobs within years.
  2. Companies have the models and tools but are getting little financial benefit because they lack a Human OS — the people, workflows, incentives, and governance that turn AI capability into real value.
  3. This gap is both an organizational and career crisis: without rebuilding how people learn and work, roles from juniors to middle managers are at risk while AI‑native workers and new ladders will rise, so act now to build human readiness.

Should Your Data Science Team be Centralized or Decentralized? Why Not Intentionally Rotate?

Mike Talks AI • 98 implied HN points • 19 May 23
đź•ą Technology Organizational Design
  1. Consider a hybrid approach for data science teams to balance the strengths of both centralized and decentralized setups.
  2. Some companies are experimenting with intentionally rotating between centralized and decentralized structures every few years.
  3. Switching between centralization and decentralization periodically allows for exploration and scalability of diverse ideas within data science teams.

Bits, Bytes, and Bylaws: Timeless Computing Laws (Part - 2)

Wisdom over Waves • 59 implied HN points • 28 Dec 23
đź•ą Technology Organizational Design
  1. Adding more people to a late software project can make it even later due to various factors like onboarding time, increased coordination needs, and additional deployments causing outages.
  2. When a measure becomes the target, it loses its effectiveness, leading to actions like renaming variables or engaging in practices that prioritize metrics over true code quality.
  3. The structure of the software often mirrors the communication structure of the organization that designed it, showcasing the impact of company dynamics on software architecture.

The art of letting go as a manager | Transcend’s Minh Nguyen

Dev Interrupted • 23 implied HN points • 12 Aug 25
đź’Ľ Business Organizational Design
  1. As a manager, it's tough to stop thinking 'I'll do it myself.' Learning to delegate helps everyone grow and makes the team stronger.
  2. Building teams around customer problems is smarter than just focusing on tech. It helps to create more effective and focused teams.
  3. Creating a 'ramblings' channel for remote teams can boost connection and creativity, making it easier for team members to share ideas.

Enterprise General Intelligence: The Emergent Mind of Organizations

Nano Thoughts • 1 implied HN point • 02 Feb 26
đź•ą Technology Organizational Design
  1. Companies need a nervous system — continuous sensing, shared memory, and homeostatic regulation — not a single omniscient center, so drift gets detected and corrected early.
  2. Culture is the organization's decision procedure, so make decision logic visible and teachable. Provide contextual memory that surfaces the right information at the moment of choice and traces provenance to resolve conflicts.
  3. Build a continuous, stateful, symbiotic system with clear governance and privacy (including a right to forget) rather than a stateless rented model or surveillance tool, because surveillance drives real thinking underground.

Is the team for you or are you for the team?

Sunday Letters • 119 implied HN points • 18 Sep 22
đź’Ľ Business Organizational Design
  1. Think of leadership like an upside-down org chart. The people doing the work should be at the top, and the manager is there to support them. It shows that the team's work is what truly matters.
  2. Managers shouldn't push team members into roles they aren't excited about. Instead, they should place people where their skills fit best, benefiting the team.
  3. The team exists to achieve goals together, not to serve the manager's needs. As a manager, your job is to help the team solve their problems, not the other way around.