Target operating model with activities and practises

Look, there are basically five things you gotta nail down: how your org is structured and who makes decisions, your actual work processes, the tech stack, how data moves around, and whether your people have the right skills. I always tell people to map out where you are now first - saves you tons of headaches later. It's honestly like building a house where you can't skip steps. Governance shows who's in charge of what. Processes are how stuff actually happens day-to-day. Tech gives you the tools. Data keeps everyone informed. Then you've got your team capabilities covering skills and culture. Once you know your current state, design where you want to be and you'll see the gaps.

So basically, a TOM is like the bridge between your big picture strategy and actually getting stuff done day-to-day. Your organizational goals are one thing, but this translates them into the real operating structures and processes you'll need. Think of it as your strategy's reality check - ambitious goals are cool, but without the operational foundation, you're kinda screwed. Every process and role gets designed to support what you're actually trying to accomplish. Honestly, most companies skip this step and wonder why nothing works. Start by mapping those strategic priorities to what you'll operationally need to pull them off.

Tech is basically what makes your whole operating model possible - it controls what processes you can actually run and how fast things move. Can't really design where you want to go without knowing what tech you'll need to get there. Your tech stack shapes everything: org structure, how quick decisions get made, customer experience. Honestly the two are so connected now it's kinda pointless to think about them separately. Just don't make the mistake of picking technology first then trying to jam your processes into it later - I've seen that go badly. Map out your future processes first, then figure out what tech gaps you have.

Honestly, set up your KPIs first before you roll anything out - track efficiency gains, cost cuts, employee happiness, customer metrics, all that stuff. But here's the thing: don't just stare at dashboards all day. Actually walk around and ask people if things feel better. I've seen too many "successful" implementations that looked great on paper but were a nightmare in reality. Quarterly check-ins work well to see what's actually moving the needle. If something's not working, pivot. The whole point is making your daily operations run smoother and align with where you're headed strategically.

Ugh, scope creep is the worst - literally everyone thinks their random project needs to be included. Getting all the stakeholders aligned feels impossible sometimes. You'll be juggling what actually exists now vs. where you want to end up, which is tricky. Don't go too deep into details or you'll never finish. Change management sucks too because people hate new processes even when they're obviously better. Oh, and teams always forget about data/tech dependencies until it's too late. Honestly? Set hard boundaries on scope from day one and get the executives on board early. Otherwise you'll redesign this thing forever.

Culture is absolutely massive for TOM design - it'll make or break your whole thing. Look at decision-making styles first (top-down vs everyone weighs in), plus communication patterns and how much risk people can stomach. I've watched gorgeous operating models crash and burn because they totally missed the "but we've always done it this way" factor. Your current culture will either speed things up or completely sabotage you. Map out those cultural quirks early and build around them instead of fighting against human nature. Trust me on this one.

Honestly, start with mapping out who actually needs input - don't forget the people doing the real work, not just executives. Workshops are your best bet for getting everyone collaborating instead of just nodding along. Senior folks usually open up more in one-on-ones than group settings. Design sprints keep things moving and interactive (way better than sitting through another slide deck). Document what people say and show them how you used their feedback - otherwise they'll think you're just going through the motions. Co-creation sessions work really well too if you can swing it.

Here's the thing - start with flexibility baked right in. Modular processes work way better than rigid ones. Cross-train your teams so they can actually pivot when stuff changes (and it always does). I'd focus on making your tech stack scalable too, honestly that's where most companies mess up. Build regular check-ins to see what's shifting in your market. Short ones work fine. Then you can tweak your structure or capabilities as needed. It's like... think LEGO blocks vs concrete foundation, you know? Way easier to rebuild later. Look at what's most locked-down in your current setup first and start there.

So basically a TOM maps out who makes what decisions at each level - no more guessing games. You'll have clear processes instead of those awful email threads where nobody knows who's supposed to approve stuff. It also sets up the same metrics everywhere so teams aren't working off different data (which honestly happens way too much). The cool part is it actually forces different departments to figure out how they'll work together on bigger decisions. I'd start by looking at where decisions get stuck in your company right now - that's probably where the TOM will help most.

Regulations aren't optional - they're basically your design constraints from the start. Map out all the rules that apply to your processes before you build anything. Don't make my mistake of creating the "ideal" model first, then trying to squeeze compliance in later. That's a nightmare. Your governance structure, data processes, risk controls - regulations will shape all of it. I know it sounds backwards, but treat regulatory requirements like actual design specs. Build them into the foundation instead of tacking them on at the end. Way easier that way, trust me.

Here's what I've learned the hard way - build flexibility into your TOM from the start. Don't make it super rigid. Review it quarterly to see what's actually working. You'll want clear rules about who can approve changes when things shift. Honestly, most companies I've worked with treat their TOM like it's carved in marble, which is just asking for trouble. Track the early warning signs, not just the after-the-fact metrics. Oh, and create an environment where people can speak up about improvements without getting shot down. Your front-line folks usually spot issues way before leadership does.

TOGAF's pretty standard for enterprise architecture stuff. Process optimization? Most people go with Lean Six Sigma. McKinsey's 7S model gets thrown around constantly - consultants are obsessed with it honestly. For actually mapping everything out, Visio and Lucidchart work great. Miro's solid for workshops too. Some bigger orgs use fancier tools like ARIS or Bizagi, but that's probably overkill unless you're doing heavy process modeling. Here's the thing though - don't get sucked into buying the shiniest tool. Pick whatever your team already knows how to use. I've seen too many companies waste months trying to learn some complex platform when they could've just started with the basics.

You absolutely need people from every department involved - seriously, don't try building this thing alone. Finance knows where the money goes, IT understands what systems can actually handle, operations sees the real bottlenecks. Each team has different insights about how work actually flows (not how it's supposed to flow on paper). I learned this the hard way once. Set up those cross-functional meetings right from the start. Otherwise you'll create something that looks perfect in theory but falls apart when real people try using it. Keep everyone talking throughout the whole process too.

Honestly, every case study I've seen shows the same thing - you need rock-solid governance and everyone on board from the start. Companies that nail communication early? Their rollouts are so much smoother. Here's what's wild though - most failures happen because people skip the "boring" foundation stuff. Can't blame them, but it always bites them later. The winners pilot small, learn fast, then adjust before going big. None of this "perfect it first" nonsense. Study how they dealt with pushback and tracked progress. That's where the real gold is for your situation.

Honestly, you can't just slap risk management onto your TOM after the fact - build it in from the start. Map out your big risks first: operational stuff, compliance headaches, cyber threats, all that fun stuff that makes you stress eat. Design your governance and controls right into the operating model itself, not some random spreadsheet nobody looks at. Build risk checkpoints into every major handoff between processes. Automate controls wherever you can (saves your sanity later). Make sure someone actually owns each risk area in your future state - accountability matters big time.