Understanding Organizational Structures

Defining Organization: Structure and Efficiency

Ruby Sturt: Hi everyone, it’s Ruby here—welcome back to the IBDP Business Management Success Podcast. You might remember in our last episode we were deep in the people side of business, chatting about Human Resource Management and why good ol’ HR is actually kind of the backbone of everything, right? Today, we’re diving into how a business gets itself organized—not just for the sake of neatness, but for real-world efficiency, kind of like… Well, imagine you’re coaching a footy team and you’ve got to decide who’s playing where, who’s passing the ball to whom, and who's, uh, sitting on the bench when it’s crunch time.

Eric Marquette: Yeah, exactly Ruby. And this whole business of formations—it’s not just for Sunday league matches. The way you set up your team, or let’s say your organization, can absolutely make or break your performance. The structure of a company is like its formation on the field: it affects how information flows, how fast decisions are made, and even, you know, how creative people can be when the pressure’s on. But before we go on, we should probably break down some of the jargon students are bound to come across.

Ruby Sturt: Great idea. It’s a bit of an alphabet soup, isn’t it? So, delegation: that’s when you give responsibility and authority to someone else to get the job done. Span of control is, basically, how many people one manager is directly responsible for. If you’ve got a wide span, you’re juggling more folks—kinda like a barista running three espresso machines at once.

Eric Marquette: Yeah, and chain of command, that’s the line up and down which orders move—from senior managers to the newest hire. Then there’s hierarchy, which is just the levels of authority stacked on top of each other, like layers in a very complicated wedding cake. Centralization means decisions get made right at the top, while decentralization lets folks lower down call a few of their own shots. Bureaucracy, meanwhile, that’s all about rules, procedures, and paperwork—sometimes necessary, but I reckon most people groan at the word.

Ruby Sturt: Don’t get me started on paperwork, mate. But here’s a term I only learned at my first summer gig—delayering. So, I worked at this tiny radio station, and one day, half the technical team called in sick right before a live show. Suddenly, we couldn’t wait for approvals from the top. Because the setup was so decentralized, the sound engineer and I literally rewired things on the fly—crazy, but it worked. That’s the sorta magic you get when people closest to the problem can just… solve it, no forms required.

Eric Marquette: Brilliant. I love that—shows how structure shapes agility, especially when unexpected things crop up. Right, so the last big concept to mention here is the matrix structure, which—spoiler alert—we’ll get into in a bit more detail soon, but it’s where you don’t just have one boss, but potentially two or more, based on projects rather than just hierarchy. It enables all sorts of creative approaches, and, as we’ll see, it’s a great fit for a fast-moving world.

Types and Uses of Organization Charts

Ruby Sturt: Okay, let’s get visual—even though you’re only hearing us, try to picture this: a flat, or horizontal, organizational chart is almost… well, flat—barely any layers between the top folks and everyone else. Your typical tech start-up, like early Spotify, loved this: it’s got a founder, maybe a couple of managers, then everyone’s pretty much reporting straight to them. Fast, simple, but sometimes a bit chaotic when things scale up.

Eric Marquette: The opposite then is a tall, or vertical, structure. Imagine a mountain with lots of steps—the classic example is a bank like HSBC. There are loads of managers in between the CEO and your frontline teller. Each manager has a smaller span of control—so decisions get filtered and can be a bit slow, but it’s highly controlled. There’s a clear path for promotions, but communication and innovation might get, well, stuck in traffic.

Ruby Sturt: There’s also another way companies organize things: by product, function, or region. Example—Apple. It’s got entire divisions for hardware and software, and even separate regional branches. So, you might have the European team focusing entirely on localization, while the hardware guys obsess over chip design in California. More layers, but super focused expertise.

Eric Marquette: Now, just to complicate things, companies like Google use something called a matrix structure—so imagine a grid instead of a pyramid. Employees can be grouped by function, project, or region, and they essentially answer to more than one manager at once. It’s a bit of a brain twister but it allows for cross-functional collaboration. You can have an engineer working on a search project and a mobile team at the same time. There was a great example when Google developed Gmail—they drew in people from various divisions, allowing innovation to flourish outside any one department’s silo. Sometimes messy, but, honestly, it’s why they manage to keep pushing out new ideas all the time.

Ruby Sturt: And that’s where your structure has to line up with what your company actually wants to achieve. Like, a really creative business might thrive with a flat or matrix chart, while a company needing absolute reliability—think pharmaceuticals or finance—might prefer staying tall. Actually, this ties right back to what we talked about in Episode 5, where we explored how different growth paths require different approaches to keeping things organized and sane as a company expands.

Adapting Structures for a Dynamic World

Eric Marquette: Honestly, structure isn’t static—not anymore, anyway. Businesses have to keep on their toes. Take Handy’s Shamrock Organization: there’s the core of permanent staff, then a ring of flexible workers, and finally outsourced specialists. It’s almost designed for the gig economy—think about Uber, right? There’s a main team running the app, but most drivers and support are flexible or contractors, so they can ramp up or down fast.

Ruby Sturt: That’s such a good point, Eric. And when you layer in project-based structures, you’re really seeing how adapting is, like, baked into survival. Whether you’re a start-up or a huge multinational, you kinda need ways to go from idea to action before the market shifts again. Which, brings us to a juicy question… Are those creative structures—like matrix or project-based—actually more suited to a rapid-fire, constantly evolving market? Or do they risk becoming total chaos if communication breaks down?

Eric Marquette: Yeah, that is a good one. I reckon creative structures give you freedom to innovate, but without knowledgeable managers keeping things together, it can all fall apart. It brings up that whole TOK angle: is ‘being knowledgeable’ essential for a manager, especially if you’re stripping out layers—delayering, as it’s called? Maybe it’s less about knowing everything yourself, and more about knowing how to connect people and information properly. It’s almost, I suppose, like being a conductor, rather than a soloist.

Ruby Sturt: I love that—so managers don’t need all the answers, but they’ve gotta know who does and nurture that network. And hey, for everyone listening, here’s a challenge for you: Next time you’re at your favourite café or looking at a brand like LEGO, try sketching out a basic org chart. Think about how roles might’ve changed when LEGO pivoted toward digital play and partnerships, versus the old days of just blocks in a box.

Eric Marquette: Brilliant exercise, Ruby. And if you want to take it deeper, try a quick SWOT analysis—strengths, weaknesses, opportunities, threats—on whichever structure you’ve mapped for that company. How does their setup give them an edge, or where does it hold them back? Oh, and don’t forget, the way an organization’s structured can also have ethical impacts—like who actually has a say in decision-making, or how transparent things are in handling staff downsizing.

Ruby Sturt: Absolutely, and we’ll definitely keep the conversation going next time. We’re tackling decision tools and more strategy, so keep your pencils and caffeine handy. Eric—always a pleasure. Say goodbye to the good folks?

Eric Marquette: Always a pleasure, Ruby. Thanks for tuning in, everyone. Sketch out those org charts, and we’ll catch you next episode. Cheers!

Ruby Sturt: See you next time, folks!