Engineering teams that spark unexpected innovation

🎁 Notion templates: "Serendipity checklist" and the "Shadow org chart worksheet"

Tanya is the Engineering Manager of a team at a fast-growing startup.

Her team builds cutting-edge features, has hired top-notch developers, and has massive potential. But despite the talent in the team, deadlines are missed, last-minute blockers appear out of nowhere, and communication feels clunky.

Tanya discovered two major blind spots:

1. Team Silos

2. Hidden Influencers

In this article, you’ll learn how to solve both problems. It’s not rocket science
You’ll also get two Notion templates to help you with that:

• Serendipity Checklist (build “lucky accidents” and fresh ideas)

• Shadow Org Chart Worksheet (spot the real decision-makers)

---

Outline

- Why silos stall innovation (and how to fix them fast)
- Engineering Serendipity (on purpose, not by chance)
- The hidden Org Chart (who truly calls the shots)
🔒 Your Templates (Serendipity Checklist & Shadow Org Chart Worksheet)
🔒 Action Steps (quick wins you can implement today)
🔒 Advanced Silo-Busting Strategies
🔒 Overcoming Resistance & Aligning Leadership
🔒 Final Thoughts

---

If you enjoy posts like this, consider supporting my work and subscribing to this newsletter.

As a free subscriber, you get:

• ✉️ 1 post per week

• 🧑‍🎓 Access to the Engineering Manager Masterclass

As a paid subscriber, you get:

• 🔒 1 chapter each week from the book I am writing “The Engineering Manager’s Playbook”

• 🔒 50 Engineering Manager templates and playbooks (worth $79)

• 🔒 The complete archive

---

Why silos stall innovation

The Problem
Engineers are busy. Everyone’s heads are down, focusing on their immediate tasks and maybe sometimes pairing with another engineer.

But this focus creates silos.
Fresh ideas rarely make it across team boundaries. I have seen teams solve the same problems in parallel. Or expect the other team to work on a service that no one owns.

What You Can Do

• Micro-Rotations: Let an engineer of your team work with a different team for a week. It’s a powerful way to spark collaboration and empathy.

• Open Demos: Host a bi-weekly “show-and-tell” where teams showcase progress and even half-finished features. Visibility and early feedback will prevent duplicate work.

Why It Matters
When silos break there are fewer miscommunications, fewer last-minute blockers, and more creative breakthroughs.

---

Engineering Serendipity (Yes, You Can Plan It)

The Power of “Lucky Accidents”
We’ve all had those magical moments where a random chat solves a big technical problem. Those moments feel lucky, but they don’t have to be random.

How to Make It Happen

• Cross-Team Coffee Chats: Use a tool like Donut to pair people from different teams every month.

• Slack Channels by Topic: Instead of separate “frontend” and “backend” channels, create channels named by challenges (like #performance-help). Watch how quickly new ideas will pop up.

Immediate Benefits
By engineering these casual conversations, you’ll see issues tackled earlier and brainstorming that leads to unforeseen innovations (minus the extra meetings).

---

The Hidden Org Chart: Who Really Calls the Shots

Why the Official Chart Lies
Your company’s org chart shows who reports to whom. But it rarely shows who can kill a project with one sentence. Sometimes it’s a respected staff engineer. Sometimes it’s a well-connected colleague who’s been there for ages.

How to Find the Real Influencers

• Ask: “Who do you go to for advice or final approval?”

• Observe: Who’s consistently mentioned on critical Slack threads or emails?

• Spot Blockers: Is there someone who can say, “We tried that before,” and everything stops?

Stop Fighting Them. Involve Them.
Once you know your true gatekeepers, bring them in early. Share updates, invite feedback, and get their buy-in before you’re in too deep.

---

Your Templates (Paid Subscriber only)

Below are the two documents that make it easy to implement the ideas above.