Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / Why New Managers Fail at Context Setting
Transcript
- Lucas: The biggest mistake I see new managers make isn't poor communication or lack of empathy. It's a failure of context setting. They treat their team like a series of execution engines, plugging in tasks and hoping for output, rather than framing the problem space so the team can solve it themselves. Luna: Right. So they become bottlenecks. Every small decision has to go through them because they haven't defined what decisions the team actually owns. Lucas: Exactly. And it's not just about speed. It's about cognitive load. When you don't set context, your team spends all their energy guessing your preferences instead of solving the actual business problem. You end up managing their anxiety, not their work. Luna: I've seen this in tech. The manager wants the feature built but never explains why it matters to the user, so the engineers build exactly what was asked, not what was needed. Lucas: That's the classic spec-following trap. Let's talk about a specific framework that fixes this: the Decision Rights Matrix. It sounds bureaucratic, but it's actually the opposite. It's about clarity. Luna: How does that differ from just telling people what to do? Lucas: It differs because it assigns ownership of the outcome, not just the action. There was a case study on a mid-sized logistics firm that implemented this last year. Before, every vendor contract under fifty thousand dollars required the director's signature. After mapping decision rights, they pushed that authority down to senior account managers, provided they stuck to pre-approved terms. Luna: So they didn't just say 'you decide.' They gave guardrails first. Lucas: Precisely. The guardrails are the context. The terms were fixed: no multi-year commitments, standard liability clauses, price increases capped at five percent per year. Within those bounds, the account manager could negotiate anything. The result? Decision latency dropped by forty percent. Luna: Forty percent is huge. That's weeks of saved time. But how do you prevent abuse when you give people that much leeway? Lucas: You rely on transparency, not approval. The matrix requires that any deviation from the standard terms be flagged and documented. If an account manager wants to sign a two-year deal, they have to write a brief memo explaining why. It shifts the manager's role from gatekeeper to reviewer of exceptions. Luna: That feels less like policing and more like coaching. You're seeing if they can justify their judgment. Lucas: It is coaching. And it scales. If you have to approve every routine decision, you can only manage three or four people effectively. Once you set the context for the routine stuff, you free up your brain for the non-routine stuff. The weird edge cases. Luna: Which brings me to the donor segment. A quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. — and that's literally what funds making these deep dives into management theory without ads cluttering the feed. Lucas: Yeah, it keeps us independent. We can talk about messy management realities without worrying about corporate sponsors pulling strings. If that resonates with how you want to consume content, check out the link. Luna: It really does help keep the signal to noise ratio high. Back to the matrix — does this work for creative teams, or is it too rigid? Lucas: It works better for creative teams, ironically. Creativity needs constraints. Think of haiku poetry. The constraint of fourteen syllables forces more creativity than a blank page. For a design team, the context might be brand guidelines, budget caps, and deadline immutability. Everything else is open. Luna: So the manager defines the box, and the team paints inside it. But what happens when the team disagrees on where the box should be? Lucas: That's the friction point. New managers often try to avoid conflict here. They just change the box to keep everyone happy. But that erodes trust. If the context changes arbitrarily, no one knows what the rules are anymore. Luna: So you have to hold the line on the principles, even if you bend on the details? Lucas: You hold the line on the process. If the team challenges the context, you bring them back to the data. Why do they think the five percent cap is wrong? What market signals suggest otherwise? You treat the context as a hypothesis, not a commandment. Luna: That turns a political debate into a strategic discussion. Much healthier. Lucas: Exactly. And it models the behavior you want. If you want your team to challenge assumptions, you have to show them how to do it respectfully, with evidence. That's part of the context too. How we disagree. Luna: I love that. 'How we disagree' is a rule I wish more teams had written down. Lucas: It's rare. Most teams just assume everyone plays nice. But in high-stakes environments, polite disagreement isn't enough. You need structured dissent. The decision rights matrix encourages this because it clarifies who has the final say. If the senior engineer says the architecture is risky, and the product manager says the deadline is fixed, someone needs to own that trade-off. Luna: Usually the manager ends up playing referee. Is there a way to avoid that? Lucas: Yes, by pre-defining tie-breakers. In the logistics example, if an account manager and a legal counsel disagreed on a clause, the matrix said legal wins on risk, sales wins on revenue. No meeting required. The manager only gets involved if the issue falls outside both categories. Luna: So you're essentially creating a constitution for daily operations. That's powerful. Lucas: It is. And it reduces burnout. Managers burn out when they feel responsible for everything. Team members burn out when they feel powerless. This balances both. You take responsibility for the framework; they take responsibility for the fit within it. Luna: But doesn't setting up a matrix take a lot of upfront time? New managers are already drowning. Lucas: It takes a few hours, maybe a day. But it saves months of firefighting. Think of it as paying a premium upfront for lower maintenance later. You sit down with your team, map the top ten recurring decisions, and assign rights. It's a collaborative exercise. The team usually helps you identify the gaps. Luna: So it's not something you impose. It's something you build together. Lucas: Always. If you impose it, it's just another layer of bureaucracy. If you build it, it's a shared understanding. That distinction matters for buy-in. Luna: What about remote teams? Does distance make context harder to convey? Lucas: It makes it harder to miss. In an office, you can read body language. You can overhear a conversation and jump in. Remote, you have to be explicit. The decision rights matrix becomes your single source of truth. It lives in a shared doc. Everyone can reference it. Luna: Documentation over intuition. That's the remote worker's best friend. Lucas: It is. And it creates fairness. In an office, the person sitting next to the manager might get more informal guidance. Remote, everyone has access to the same written context. It levels the playing field. Luna: That's a subtle but significant equity issue. I hadn't thought about it that way. Lucas: Management is always about equity. Who gets heard? Who gets trusted? Who gets space to fail? The matrix answers these questions structurally, not emotionally. Luna: So it removes the guesswork from trust. You either have the right, or you don't. Lucas: Precisely. And if you don't have the right, you know who to ask. It's efficient. It respects everyone's time. It's the opposite of micromanagement. Luna: Micromanagement is just context-setting failure dressed up as care. Lucas: That's a good line. Micromanagement is fear disguised as diligence. When you set clear context, you remove the fear. You signal that you trust their judgment within the bounds you've set. Luna: Does this scale to larger organizations? Or is it just for small teams? Lucas: It scales. In fact, it's essential at scale. Large companies drown in ambiguity. Every department has its own siloed context. Cross-functional projects fail because nobody knows who decides what. A standardized decision rights framework across the org can align everyone. Luna: Like a universal grammar for business decisions. Lucas: Exactly. It allows different departments to speak the same language. Sales knows what they can promise. Engineering knows what they can build. Legal knows what they will block. Friction disappears. Luna: So the new manager's job isn't to do the work, but to design the system where the work happens. Lucas: That's the shift. From player to architect. It's harder because you can't hide behind individual contribution. Your output is the team's output. If the context is bad, the team fails. If the context is good, the team thrives. Luna: It puts the spotlight squarely on leadership design. No more hiding. Lucas: No more hiding. And that's scary for some. But it's also liberating. You stop being the hero who saves the day. You become the facilitator who ensures the day is saved by the team. Luna: A facilitator of freedom, rather than a controller of chaos. Lucas: I like that. Freedom within a framework. It's the sweet spot of modern management. Luna: So for our listeners stepping into management tomorrow, what's the first step? Lucas: Start small. Pick one recurring decision. Define the context for it. Assign the right. Communicate it clearly. Then watch what happens. You'll likely see a burst of energy from the team. They'll finally feel owned by their work. Luna: One decision at a time. Build the habit of clarity before building the empire. Lucas: Build the habit of clarity. Because without it, everything else is just noise. Luna: Do you think AI tools will eventually automate this context-setting for us? Lucas: AI can help draft the matrix. It can analyze past decisions and suggest patterns. But it can't understand the nuance of human relationships or the political landscape of your organization. The context is always social, not just structural. Luna: So the human element remains central. The tool supports the judgment, it doesn't replace it. Lucas: Correct. AI gives you data. You provide the wisdom. The combination is powerful, but the wisdom has to come from you. Luna: Wisdom over data. That's a good reminder as we wrap up. Lucas: As we wrap up, think about the decisions you're currently holding onto. Which ones could you release if you just wrote down the rules? What would change if you stopped approving and started framing? Luna: It's a question worth sitting with. Especially if you're feeling overwhelmed. Lucas: It is. Overwhelm is often a symptom of unclear boundaries. Clear boundaries create space. Space creates performance. Luna: Space for the team to breathe. And for you to lead. Lucas: Exactly. See you next time.