The $100M Entrepreneur Podcast

Episode: Build The Organization BEFORE You Build The Team

27 min Listen to the original
Organizational DesignBusiness ScalingFounder StrategyManagement StructureOperational Efficiency

Summary

The speaker argues that businesses should design their organizational structure based on future goals and necessary functions rather than current personnel. He introduces the 'function before person' principle, advising founders to identify required roles and outcomes before hiring. The discussion covers scaling models, future pacing to identify bottlenecks, and the distinction between job descriptions and positional contracts. The speaker emphasizes that true businesses must operate without the founder's constant involvement and recommends specific exercises to align structure with strategy.

Key takeaways

  1. 1
    The speaker asserts that if you want to double or triple your business size, you cannot simply add people to the existing structure; you must stop asking what you have and start asking what the business needs to be.

    Unidentified speaker (speaker_0) · 0:59

  2. 2
    Then what position owns that result? Then what does great performance in that position look like? Then who's the best person to do it?

    Unidentified speaker (speaker_0) · 2:39

  3. 3
    That's not organizational design, that's organizational archaeology for want of a better term.

    Unidentified speaker (speaker_0) · 3:39

  4. 4
    'Future pacing' involves identifying structural constraints before they become emergencies. The speaker suggests asking what breaks at 2x, 5x, or 10x sales/employees to proactively design the next structure.

    Unidentified speaker (speaker_0) · 6:57

  5. 5
    Every year, I want you to try to remove your name from another box or another two boxes type thing, or every quarter, not because you're lazy. because you're moving to higher value work. In the beginning, you do the basic one-to-one sales, then you build sales team and sales systems, then you build a sales manager and a CSO type thing. And so if if you then lead the sales manager, eventually maybe you barely touch sales operations. You didn't stop caring about sales. You didn't get lazy. You build an organization capable of producing sales without you. And that's the goal.

    Unidentified speaker (speaker_0) · 8:39

Episode sections

  1. 0:00 – 2:19

    The Backwards Organization Chart

    The speaker describes how most businesses hire people first and then assign roles, leading to messy, reactive structures. He argues that organizations should be designed based on future goals rather than current personnel, emphasizing that function must precede person.

  2. 2:19 – 6:37

    Designing for Future Scale and Functions

    The speaker advises starting with business goals and identifying necessary functions (e.g., marketing, sales, ops) rather than existing people. He introduces the 'X times Y' scaling model, suggesting that organizational structure must change as the business replicates across locations or units.

  3. 6:37 – 7:59

    Future Pacing and Bottleneck Identification

    The speaker recommends 'future pacing' to identify structural constraints before they cause failure. He suggests asking what breaks at 2x, 5x, or 10x scale to proactively restructure, rather than reacting to crises like customer complaints or owner burnout.

  4. 7:59 – 11:18

    Founder Evolution and Accountability

    The speaker highlights the danger of founders remaining in operational boxes as the company grows. He defines a true business as one that works without the owner and emphasizes that the org chart must show clear accountability for results, not just hierarchy.

  5. 11:18 – 14:01

    Position Contracts vs. Job Descriptions

    The speaker distinguishes between job descriptions (tasks) and positional contracts (outcomes/authority). He argues that responsibility must be paired with appropriate authority to be effective, and that every position needs clear KPIs and reporting lines.

  6. 14:01 – 17:02

    Decision Rights and Span of Control

    The speaker discusses the importance of defining who decides versus who recommends to avoid bottlenecks. He notes that too many direct reports reduce management quality and that structure should be designed for effectiveness, not just flatness.

  7. 17:02 – 21:19

    Titles, Capability, and Strategy Alignment

    The speaker warns against promoting titles faster than capability and advises that structure follows strategy. He explains that centralized vs. decentralized decisions depend on the specific business model and that technology can dramatically alter organizational needs.

  8. 21:19 – 26:48

    The Two-Chart Exercise and Five Questions

    The speaker outlines a practical exercise: drawing a current 'brutally accurate' org chart and a future 'goal' org chart. The gap between them forms the development plan. He concludes with five questions for every role: result, capability, authority, who, and when.

Claims worth verifying

Brad Sugars is described as the #1 business coach in the world with a 30-year career.

Unidentified speaker (speaker_0) ·0:00

How to verify: Check the podcast show notes or Brad Sugars' official website/bio for self-described titles and career length. For recent events, verify 2026-08-18 through 2026-11-18. Use another period only when the speaker explicitly names it.

Do your own research

  • Review the specific 'X times Y' scaling model to see if it applies to your industry's replication dynamics.
  • Compare your current job descriptions against the 'positional contract' framework to identify gaps in authority and outcome definition.
  • Audit your org chart for 'organizational archaeology' by checking if roles exist due to strategic need or historical/personal reasons.
  • Calculate your current 'span of control' to determine if direct reports are reducing management quality.
  • Identify potential bottlenecks by simulating 2x, 5x, and 10x scale scenarios for sales and headcount.
  • Verify if your decision rights are clearly defined versus recommended to avoid operational delays.
  • Check if your titles align with actual capability levels rather than tenure or hierarchy.
  • Assess whether your technology stack supports the proposed centralized vs. decentralized decision structure.
Full transcriptexpand
0:00
Unidentified speaker (speaker_0): Let me give you one of the strangest ways businesses build organizations. Very weird. They hire somebody and then they work out what that person should do. Then they hire somebody else, and guess what? Then they move some responsibilities around and they go, okay, then somebody leaves, so they give half the job to Mary and half to
0:19
Unidentified speaker (speaker_0): Bob, and away we go, sort of thing. Then Bob gets promoted, so Mary gets all of the work. The owner takes three. more responsibilities on board, and someone else gets hired because everybody's overwhelmed. And uh five years later, uh they draw the organization chart to explain the mess that they've created.
0:39
Unidentified speaker (speaker_0): Yeah, that does happen. It's backwards. Your organization shouldn't simply, you know, tell me what your company does. That's an org old chart that's built backwards type thing. It should help you build the company you need tomorrow. That's what we're talking about today, okay? How do you design an organization
0:59
Unidentified speaker (speaker_0): capable of supporting the business, achieving the goals of where you're trying to go? Not the company you've already built, the company you're building next. Because if you want to double or triple or five times or ten times. the size of your business, you cannot just keep adding people to your
1:19
Unidentified speaker (speaker_0): structure. At some point, you have to stop asking, you know, what do we have and start asking, what does the business need us to be? You know, I've always thought of it as my role as a leader. Who do I need to be in order to build the company that I'm aiming to build? And it's the same for my people, the same for my managers, the same for my leaders, and the same for yours
1:39
Unidentified speaker (speaker_0): as well. So, you know, when you think about it, most org charts are just history documents. Thinking about, you know, the CEO at the top, a few managers underneath, and people underneath them, lines connecting everybody. Great. But usually the chart was drawn after the organization already existed. Its documentation or the documentation of
1:59
Unidentified speaker (speaker_0): what existed tells me who's currently working. works here. But and yeah, that's useful, okay? But it doesn't necessarily help us grow. I want the future org chart, okay? I want the organization chart that says this is what the business needs to look like when we reach our next destination. This is a
2:19
Unidentified speaker (speaker_0): completely different tool sort of thing. If you start with the business and not with the people, start with the goals, not with the people. This is the biggest principle in organizational design. Function before person. Don't start with Mary's great. What can Mary do? Start with what is the business need done.
2:39
Unidentified speaker (speaker_0): Then what position owns that result? Then what does great performance in that position look like? Then who's the best person to do it? Maybe it is Mary. maybe it is Bob, maybe not. You know, you look around and you think, see, that's the discipline because if you build roles around
2:59
Unidentified speaker (speaker_0): existing people, you eventually create an organization that's almost impossible to understand. All right, so hang on, let's get this one out of the way first. The family business problem, right? Particularly in founder-led family businesses, this stuff happens because. someone joins because they're available and they're related. You know,
3:19
Unidentified speaker (speaker_0): can you help me with the book? Sure, I'll and then I'll help with HR and then office management, then purchasing. It's your sister or your brother-in-law or your next door neighbor's dog walker's son. Then suddenly they're head of finance, HR, they're the head of purchasing or ops. Why? Because there was a strategic decision that those
3:39
Unidentified speaker (speaker_0): four functions belong together? No, of course not. Because history happened, okay? That's not organizational design, that's organizational archaeology for want of a better term. Let's dig it up. You know, you're digging through 15 years of decisions trying to work out why anybody does anything.
3:59
Unidentified speaker (speaker_0): Draw the future. Okay, think about the goal. So here's what I want you to. do, okay? Imagine the business is already at the next level. Maybe you're doing 5 million today and you want to do 20 million, or maybe you're at two and want to do 10, right? So when you think about this, if you're going from 50 to 100 million, whatever the numbers
4:18
Unidentified speaker (speaker_0): are, imagine you're already there. Now ask, what functions does this business require when we're at that level? Not who works here now, what functions will it require at that level? And when you think in functions, almost every business needs some version of
4:38
Unidentified speaker (speaker_0): marketing, sales, ops, delivery, finance, and admin people, customer experience, leadership. Like depending upon your industry, there may be technology. there might be some other things, but product development might be there, manufacturing, logistics, legal compliance, like
4:58
Unidentified speaker (speaker_0): all of these functions. Whatever of those applies to you, and whatever others do as well, but start with functions, okay? What must the business perform brilliantly to achieve the strategy? That's the organization that you're looking at. to build. Now, my way of building a business, if you go
5:18
Unidentified speaker (speaker_0): back to strategy here on the pod, is X times Y. See, it's one of the simplest ways I think about scaling a business. X times Y, where X is the successful business unit. It might do, say, you know, 3 million a year or 20 million a year type thing. Now, the why Y is how many times you replicate that, how
5:38
Unidentified speaker (speaker_0): many C. cities, how many countries, how many stores, et cetera, type thing. Now, organizationally, that does matter because you're gonna form one location to 20 locations. You can't just take today's org chart and make everybody 20 times busier type thing. You can't just replicate everybody
5:57
Unidentified speaker (speaker_0): 20 times either. The structure has to change. Maybe you need regional managers. maybe a centralized finance and accounting or marketing. Maybe you take sales as half local and half national, sort of thing. Maybe this see, because scale changes an organization. Maybe there's even a different
6:17
Unidentified speaker (speaker_0): operating structure, sort of thing, but the organization has to be designed around that future. So you're building for 2x, 5x, 10x, 16x. whatever the number is. And if you think of this as a useful exercise, you look at your current org and ask, okay, what breaks at two times? What breaks at five times? What
6:37
Unidentified speaker (speaker_0): breaks at 10 times? At double the sales, does finance break? Is at five times the the customers, does customer experience break? At 10 times the employees, how does HR break? Or does it break at three locations? How does shipping break at 20 locations? How does
6:57
Unidentified speaker (speaker_0): management break? Or does the CEO become the bottleneck? So it's that future pacing is what it's called. You're trying to identify structural constraints before they become emergency. So don't wait for the pain to create the next structure. You create it beforehand. Most businesses will reorganize
7:17
Unidentified speaker (speaker_0): after something breaks. Customer explain, you know, if if customer complaints explode type thing, staff turnover jumps, and the owner, you might be working 80 hours a week, and managers can't cope. These sorts of things, and it's like we need to restructure. Brad, margins have fallen. Yeah,
7:37
Unidentified speaker (speaker_0): three years ago you needed to restructure.
7:39
Unidentified speaker (speaker_0): Great organizations get ahead of the curve, they get ahead of the growth. You build the capacity before the business gets overwhelmed with today's structure. Not years before, but early enough. And the owners usually in too many boxes, obviously, in the current chart. If you draw your current organizational Organization chart and be honest, how
7:59
Unidentified speaker (speaker_0): many boxes have your name in them? You're the CEO, you're the head of sales, head of marketing, CMO, you know, like these are the things. If you're still chief recruiter and chief product development person, whatever it is, in the early days, by the way, that's normal, right? Of course it is. You can't employ 10 executives unless you've raised a billion dollars, you know,
8:19
Unidentified speaker (speaker_0): when the company's barely paying you. But here's the danger, though, right? The business grows and your name never leaves the boxes. If that that's what ends up happening, that becomes problems. So instead of building an organization, you simply get busier, you carry more of the load, and that's not scale. Obviously, the goal is to remove your name from many of
8:39
Unidentified speaker (speaker_0): those boxes. And there's a fun way to think about the your org chart. Every year, I want you to try to remove your name from another box or another two boxes type thing, or every quarter, not because you're lazy. because you're moving to higher value work. In the beginning, you do the basic one-to-one sales, then you build sales team and sales systems, then
8:59
Unidentified speaker (speaker_0): you build a sales manager and a CSO type thing. And so if if you then lead the sales manager, eventually maybe you barely touch sales operations. You didn't stop caring about sales. You didn't get lazy. You build an organization capable of producing sales without you. And that's the goal. Your role
9:19
Unidentified speaker (speaker_0): changes as the business changes. You know that the founder's role evolves into something different. In the beginning, you're the worker, then you're the manager, then you're the leader, then CEO, and eventually perhaps the chairperson or coach, owner, investor, whatever terminology, right? Each stage requires letting go of the
9:39
Unidentified speaker (speaker_0): previous stage. Okay. And that's hard because you're often very good at the previous job. And you might love selling, love designing, love coaching, love engineering, love working with customers. Fine, you can still do some of what you love, but don't confuse what you enjoy doing that with You know, what the business
9:58
Unidentified speaker (speaker_0): requires you to own, you as the owner, you as the CEO. to do. Those are totally different questions, right? So the org chart is really about accountability, not a good organization chart doesn't just show hierarchy, it shows accountability. Who owns what? And that's what's important to me. I think
10:18
Unidentified speaker (speaker_0): that's the real question. If something goes wrong in marketing, okay, who owns the result? If sales misses budget, who owns it? If delivery quality drops, who owns it? If someone needs a pat on the back, who owns it? Sort of thing. Everything is owned by somebody, good and bad. So one result,
10:38
Unidentified speaker (speaker_0): one owner is sort of the simplistic way I like to think about it. For every major result in the organization, I want one person ultimately to be accountable for that. Other people may contribute, of course. Marketing might help sales, sales might help product and design, you know, ops might help uh customer experience, but ultimately,
10:58
Unidentified speaker (speaker_0): who owns the number, who owns the measure, who owns the result, and that's clarity. And that's why it's positions before people. See, once you've designed the functions of the business, right, start designing the positions after that. Once positions, you know. I mean, think about it. What positions does each function require?
11:18
Unidentified speaker (speaker_0): Let's say sales, maybe chief sales officer, maybe a sales manager, salespeople, sales support. Depending upon your business, these are going to be different. And then ask, what is each position there to achieve? Not what are they there to do? What are they there to achieve? That's where we move beyond the org chart to what I call a position or contract. Now, why a contract?
11:39
Unidentified speaker (speaker_0): Because, in my opinion, it's all about what they need to achieve. And this is one of the best tools I've taught for years: the position or contract. Think of it as clarity for the role. It answers why does this position exist? What outcomes is it responsible for? The position, not the person. What duties sit within this? What authority does this position have? What are the
11:59
Unidentified speaker (speaker_0): KPIs?
12:01
Unidentified speaker (speaker_0): Who do they report to? Or what sorry, what does this position report to type thing? Who reports to it on the opposite side of it? What does success look like? See, this is dramatically better than here's your job description, what you need to do. Job descriptions and personal contract, positional contracts are different. Job descriptions tells you what to do.
12:21
Unidentified speaker (speaker_0): A positional contract tells you what you're accountable for, what you have to achieve. That's a massive difference. Job description: manage customer service team. Positional contract, maintain customer satisfaction above a score of X, response time below Y, and retention of customers above Z. Now
12:41
Unidentified speaker (speaker_0): we manage performance. That clarity changes everything about an organization. Responsibility without authority just doesn't work. though. And here's a I think here's a mistake organizations constantly make. They give someone the responsibility, but no authority. You're responsible for hitting this number. Great.
13:01
Unidentified speaker (speaker_0): Can I make this decision? No. No. Can I spend this? No. No, you can't do all of that stuff. Can I change this process? No, no. Can I hire anyone? No. They're not really responsible at that point. They're not really accountable at that point. They're accountable for a result they can't control. And that doesn't work. Responsibility and
13:21
Unidentified speaker (speaker_0): accountability have to come with authority. Okay. They need to be aligned. And that's why it's a position contract. It's not unlimited authority, obviously. It's appropriate authority based on what it is. And so, you know, authority, let's go the other way. Authority without accountability doesn't work either. Like the opposite's ego. equally just as dangerous if you ask me.
13:41
Unidentified speaker (speaker_0): Someone has the ability to make decisions, but no measurable outcome. That's freedom without responsibility. So every position needs clear outcomes, clear authority, clear measurements. That's how mature organizations operate, right? Think about it this way, okay? One of the best questions you can ask in an organizational design is this: who
14:01
Unidentified speaker (speaker_0): gets to decide this, right? Pricing, hiring, discounting, refunds, marketing spend, purchasing, customer exceptions. Who gets to decide capital expenditure? Who decides promotions? There's a difference between who recommends and who decides, right? So if you think of it with those things, there's people that need to be
14:21
Unidentified speaker (speaker_0): informed, people that recommend, people that decide. And many businesses aren't slow because their people are slow. they're slow because nobody knows who can make a decision. So everything moves upward, usually to the actual owner of the business. And the the founder becomes the approval and disapproval department. And that's a classic growth
14:41
Unidentified speaker (speaker_0): problem. Slow as growth imagin.
14:43
Unidentified speaker (speaker_0): You just can't imagine how slow companies like that operate. Or maybe maybe you can. See, the owner says, I don't understand why everyone keeps coming. to me because you've trained them to. You know, you've created an approval process or threshold so low that nobody can do or decide anything. Every discount, every purchase, every hire, every decision,
15:03
Unidentified speaker (speaker_0): eventually you're spending the whole day saying, Yes, no, yes, no, maybe, maybe, yes. That's not CEO work. That's an approval. The A stamp department push decisions to the lower. lowest competent level. That's how you create speed. Okay, span of control 100% matters in business. It's it's it's
15:23
Unidentified speaker (speaker_0): another organizational concept, I guess. How many people report directly to one person? If you can push the decision making lower, and there's no magical number of how many should report to you. It depends on complexity, experience, role systems, but eventually, too many direct. reports reduces management quality, okay? If you've got
15:43
Unidentified speaker (speaker_0): 20 people reporting directly to the owner, are you genuinely managing all 20? How are you doing the weekly meetings and the weekly coaching sessions with them? It's usually a sign you need another layer, not bureaucracy, actual management. Layers are not automatically bad. I hate it when I see that happen. People say, oh, you know, I want to flat a organize. flat
16:03
Unidentified speaker (speaker_0): organization because Ricardo Semler wrote that book way back when. Sounds great until 150 people directly report conceptually to the founder. The goal isn't flat, the goal isn't hierarchical, the goal is effective. You need structure for communication, accountability, decision-making, development. Without unnecessary
16:22
Unidentified speaker (speaker_0): bureaucracy, of course, build what the strategy requires. And you've got a professional. to professionalize management as you grow. There's a stage in the business when informal management stops working, okay? When it's when it becomes a bottleneck. You just can't shout across the room. You can't know what everyone's doing. You can't personally train everybody. You
16:42
Unidentified speaker (speaker_0): need managers. You need a business operating system. It's why we built the Action Coach Business Operating System. Show Eventually you need leaders. That doesn't mean become becoming corporate for the sake of it. It means reorganizing the scale requires structure. And you know, that's what happens. When you recognize that scale requires
17:02
Unidentified speaker (speaker_0): structure, the business has outgrown improvisation or improvisational management, reactive management. But also don't promote titles faster than capability. It's another problem that uh I see, you know, a small company, 10 employees, careful. Titles should reflect actual scope and accountability because as a company
17:22
Unidentified speaker (speaker_0): grows, you may discover your chief marketing officer was really a marketing executive or a marketing manager. Now you need a genuine CMO, and you've got to, well, you've created an emotional problem for yourself. Think ahead. Use titles respectfully, okay, and responsibly. People may outgrow roles, and that's. okay. And roles may outgrow people. This
17:42
Unidentified speaker (speaker_0): is one of the hardest realities of scaling in my books, and I've had to learn it multiple times. Sometimes the person grows faster than the role. Great. Give them more, okay? Give them responsibility. But sometimes the role grows faster than the person. That's harder. Someone has As fantastic running a 10-person
18:00
Unidentified speaker (speaker_0): division may struggle at running a 20-30 20, person. 30, 40, 50 people division. Someone who ran marketing at a million can't run it at a hundred million type thing. That doesn't make them a bad person or bad at their job. It means the role changed. And leadership, you have to be honest about that. So demotion is not always a failure, right?
18:19
Unidentified speaker (speaker_0): It doesn't have to mean failure. Sometimes, you know, someone can remain incredibly valuable in a narrower role, in a smaller role. A person may be a brilliant divisional manager, but not the right executive for the whole company. And if we treat every role change as humiliation, we lose great people unnecessarily. Find where people can win. But don't
18:39
Unidentified speaker (speaker_0): leave someone in a role beyond their capability just because the conversation's uncomfortable. The entire team, the entire company pays for that laziness or lack of desire to have that. conversation. That's why build around strategy. You know, build the organization around strategy. And this is really the big idea,
18:59
Unidentified speaker (speaker_0): I guess. Structure follows strategy. And if your strategy is one premium location, your organization looks one way. If your strategy is a hundred franchises or different or org uh the you know, it's a different organization if your strategy is acquisition-based. acquisition based, different again. If you, you know, if your strategy is software,
19:19
Unidentified speaker (speaker_0): different to your strategy is global licensing, different, you know. Don't copy someone else's org chart because it looks impressive. Design an org chart that's required to execute your strategy and your goals, okay? And this comes back to like centralized or decentralized as you scale, this becomes an important decision. What should we
19:39
Unidentified speaker (speaker_0): what should be centralized? What should be remain local? What maybe finance centralizes, maybe marketing centralizes, uh, maybe HR centralizes, but customer relationships stay local. Maybe sales is local, maybe operations varies type thing. There isn't one answer. The question is the one answer, really.
19:59
Unidentified speaker (speaker_0): What creates the best combination of consistency? Speed. customer experience, economics for the business, and accountability? So design deliberately for that. And again, even systems change the org chart. Add a new piece of software, and you might remove a whole division of the department, sort of thing. Technology can change
20:19
Unidentified speaker (speaker_0): structure dramatically. If software automates a function, maybe you need fewer people. If AI can perform routine work, maybe roles become higher level. If systems centralize information, maybe management spans can increase. And don't build tomorrow organizations with yesterday's assumptions about work and yesterday's assumptions
20:39
Unidentified speaker (speaker_0): about technology. How do we make humans actually do work that is effective for the organization? What can systems do? What can AI do? What can outside specialists do? And then build the organization. And you don't have to employ everyone. I think that's an important lesson as well. Big organizational shift these days. Not every box needs to
20:59
Unidentified speaker (speaker_0): be a full-time employee. It could be an agency, it could be a contractor, a fractional executive, a partner, outsourced specialists, an agency. See. The question isn't who do we employ? The question is how does this function get done brilliantly? Sometimes employment is the answer, sometimes it isn't. If you build your future org
21:19
Unidentified speaker (speaker_0): chart, it doesn't have to have positions all the time. If we make this practical, right? Let's think about this. Take a blank sheet at the top, write the three-year goal, okay? Revenue, objective, key result, that sort of stuff. Whatever the major business target is that that really matters, then pretend you already achieved it. Okay?
21:39
Unidentified speaker (speaker_0): Now ask what functions exist in the company, okay? And the functions don't have to be jobs. Remember, we're looking at functions, okay? What departments, what leadership roles might there be? What management roles might there be? What frontline roles? Draw it. No names, just positions, just functions, okay? Then
21:59
Unidentified speaker (speaker_0): you have to add outcomes. Don't go to people again, okay? For every major box, write what is the position accountable for. One sentence, break it down. Marketing, create sufficient, profitable demand sales, converts demand into profitable customers. And you probably want to put numbers to this, right? Operations deliver the promised product or
22:19
Unidentified speaker (speaker_0): service consistently and profitably. Finance protects cash, reporting, and financial performance. Like these are the things you would write in the boxes. People ensures the organization has the talent and capability required. Whatever's appropriate for your business. Now the chart starts to become meaningful. Then think about adding names. Okay, only now. Who currently
22:38
Unidentified speaker (speaker_0): has the capability for that? Who could grow into that role? Who needs development? Where are the gaps? Which roles require external recruitment? uh, Which roles don't exist yet? Now you start to have a people plan and an org plan sort of thing. Then find your own name. Where does your name? Finally, circle that that box,
22:58
Unidentified speaker (speaker_0): okay, with your name in three years' time. Which one will you be in? And that's your development plan. What have you got to learn? Uh, some boxes you you may keep, some you may delegate. Some require a future hire, some require an agency, some are internally developed.
23:16
Unidentified speaker (speaker_0): But over time, um, now you've got to make sure you sure your name moves onward and upward and outward toward the work only you should be doing. That's why it's sort of a two-chart exercise. Is if you think about your action today, right? I want two organization charts I'd like you to have. Chart one today, brutally accurate,
23:36
Unidentified speaker (speaker_0): no titles, who actually does what? If you do marketing, put your name there. If you do finance manager, handles HR, then show it. Reality, exactly where it is today. Chart two, that future one. Okay. Three years, four years, five years, whatever the next major milestone is for you. What does a business need to look like? Then compare the two. The gap
23:56
Unidentified speaker (speaker_0): between those charts is the organizational development plan, where we are now, where we need to be. This is what we got to develop. So again.
24:03
Unidentified speaker (speaker_0): end of the pot, five questions. Let's write them down. For every major role on that future chart, ask these things. One, what result does this role own?
24:13
Unidentified speaker (UNKNOWN): Okay,
24:14
Unidentified speaker (speaker_0): result. Number two, what capability does it require? Capability. Number three, what authority does it need? Authority. So result, capability, authority. Number four, who? Who could fill it right now? If anyone, okay. Then the fifth, when do we need it? Okay. When do we need this position? Now you're designing growth. The business should eventually work without you,
24:34
Unidentified speaker (speaker_0): is ultimately the thing for the CEO or the owner of the business type thing. So if that's the ultimate goal, my definition of a business, remember, a commercial, profitable enterprise that works without you. If you have to be there, it's not a business, it's a job, and you work for a crazy person, right? You can't achieve that if your name occupies seven boxes on the org chart. It just doesn't work. You can't
24:54
Unidentified speaker (speaker_0): achieve it if every decision comes upward to you, the authority question. You can't achieve it if nobody knows who owns what. You can't achieve it if a job exists because the history rather than strategy. A business that works without you is the struct has that structure we've been discussing. Clear roles, clear accountability, right up front,
25:14
Unidentified speaker (speaker_0): clear. authority right up front, capable people, systems, leadership, management. That's what creates freedom. Most businesses build their organization backwards. We know that. They collect people, they create roles around them, then add responsibilities, then patch problems, okay? Then eventually they draw an organization
25:34
Unidentified speaker (speaker_0): chart explaining what happened over the years. Don't do that, okay? Start with the future. Where are we going? What strategy gets us there? What organization does the strategy require? What functions do these goals need? What positions? What outcomes? What authority? What measurement? Then ask: who
25:54
Unidentified speaker (speaker_0): do we need to become that organization? Who do we need to grow into? And who do we need to hire, if that makes sense? And finally, where should the founder? sit? A chairperson, coach of the business, CEO. In my case, I don't sit at the CEO role. I sit at the content creator role. That's what I love doing. Your goal isn't
26:14
Unidentified speaker (speaker_0): to create a bigger job for yourself. Your goal is to create an organization capable of producing results without everything flowing through you. So don't build an organization around the people you happen to have now. Design the organization. you're determined to become. Then develop and recruit the people capable of building it. And every year try to remove your name from
26:34
Unidentified speaker (speaker_0): another box because the organization chart shouldn't simply show you where everyone works. It should show you the path to a business that works without you.
This page was produced automatically: the audio was transcribed with nvidia/parakeet-tdt-0.6b-v3+sortformer-v2.1 and interpreted by Qwen3.6-35B-A3B-UD-IQ3_S.gguf. Transcription and interpretation can contain errors; always confirm against the original episode. Nothing here is investment advice.

More from The $100M Entrepreneur Podcast

All insights