Balancing Transparency and Process in Engineering Leadership

As Chief Engineer of strategic ballistic missile submarine USS Kentucky, I felt I had to have every answer. I was in every action, every system, every repair. The stakes were too high for anything less. But here’s the truth: that approach was untenable. No single person can shoulder that weight forever. What saved me—and what made our team world-class—wasn’t my control. It was: ✅ Delegation — trusting officers and sailors to own their watch. ✅ Intent-based leadership — giving clear direction, not micromanagement. ✅ Trust-based communication — speaking up early, listening deeply. ✅ Transparent expectations — clarity about what “good” looked like. ✅ Deep but meaningful checking — not hovering, but verifying. Scaling your business is no different. Early founders often try to be in every decision, every hire, every customer interaction. But just like on a submarine, that weight will break you—and stall your team. The transition from “I control everything” to “we achieve everything together” is what transforms brilliant engineers and scientists into enduring leaders. 💡 Where are you in that journey—holding every answer, or scaling through trust? #Leadership #ScalingUp #Delegation #ExecutiveCoaching #EngineeringLeadership #CoreX #Trust #IntentBasedLeadership #focalpountcoaching

In fragile seasons, leaders are often asked to project certainty. But certainty isn’t what builds trust. Clarity of process does. Everyone needs to know directionally where to go and how we’re getting there. Over the years, I’ve found that when outcomes feel unstable, people don’t need a confident prediction, they need to know how you’re making decisions. - Are you taking in diverse inputs? - Are you naming tradeoffs? - Are you adjusting in public, or pretending you’re not? In times of uncertainty, transparency is a stabilizer. We can’t control volatility. But we can model how to move through it, with clarity, care, and structure. That’s where real leadership lives.

“You fixed the product team.” Not exactly. Six months into a new product leadership role, someone said this to me. And while I appreciated the compliment, the truth is more nuanced. When I joined, the product development culture was a mess: ➤ Leadership was frustrated that nothing ever seemed to get done. ➤ Engineers were frustrated—they wrote code that never shipped. ➤ Product managers lacked autonomy—unable to dig into customer problems or solve them. There was no clear process to align on priorities. Product had little voice in what should be worked on, and top-down projects were often decided behind closed doors—only to change week to week. With no space for proper discovery, pressure fell on engineering to deliver against unclear, shifting expectations. Tension between product and engineering grew. But the right people were there: 👉 Product Managers who were customer-centric and solutions-oriented 👉 Engineers who cared deeply about building great software 👉 Leadership that understood the importance of prioritization and tradeoffs So no—I didn’t fix the team. I created the conditions for them to thrive. ✅ Transparency & Trust: Introduced a clear, transparent planning process with regular roadmap check-ins so leadership could align and understand progress. ✅ Product Empowerment: Gave PMs problems to solve—not prescriptive solutions—so they could do meaningful discovery on the best approach. ✅ Engineering Partnership: Brought engineering into the process early to set realistic expectations and surface platform needs. The talent was always there. They just needed clarity, trust, and runway.

Great engineering leadership isn’t about solving everything. It’s about creating the conditions where your team can. In my early leadership days, I thought I had to walk in with the answers. Over time, I learned something better: Most engineers don’t need hand-holding. They need clarity, context, and trust. Here’s how I lead now (and what’s worked): 1. Present the problem, not a pre-baked solution. → Engineers are problem-solvers. Don’t rob them of that. → Instead of “We need to use Kafka here,” say: “We need async processing at scale. Thoughts?” 2. Share constraints early. → Be open about deadlines, budget, team bandwidth, or tech debt. → Constraints help the team make realistic design choices. 3. Make room for trade-off discussions. → Your job isn’t to rush decisions. It’s to ensure good ones. → Let the team think through latency vs cost, monolith vs microservices, etc. 4. Guide the decision, don’t dictate it. → Ask: “What risks do you see?” or “What’s your fallback plan?” → Step in only when clarity or urgency is needed. 5. Protect builder time. → Cut unnecessary meetings. Shield them from noise. → Innovation dies in a calendar full of status syncs. Leadership is knowing when to speak and when to listen. You don’t earn trust by having all the answers. You earn it by helping your team find better ones.

In any leadership role, there comes a point where you have to recognise that you wear two hats. There is the “team” hat: the one you wear when you are part of the group, contributing ideas, listening to others, exploring possibilities as peers. And then there is the “leader” hat: the one you put on when, after all the debate and discussion, a conclusion still has to be reached and a decision made. I learned, not always comfortably, that being explicit about which hat you are wearing matters more than most leaders realise. When people don’t understand why a decision has been taken, they rarely give it the benefit of the doubt. They fill in the gaps for themselves, and human nature being what it is, they tend to fill them with the worst possible interpretations. An executive coach once gathered feedback from people I had worked with, and pointed out something I had never noticed: where people occasionally mistrusted my intentions, it was usually because they didn’t understand my reasoning. Once I started to make that reasoning visible, to say - “I’ve heard all sides, here’s how I’ve weighed them, and here’s why I’ve decided this way” - the atmosphere changed. People didn’t always agree, but they understood. Transparency doesn’t dilute authority; it deepens trust. Leadership isn’t about pretending to have one hat or the other all the time. It’s about having the awareness and humility to change hats when the moment demands it.

🧠 You can’t share every doubt without destabilizing others This is one of the loneliest lessons of leadership. And one of the least discussed. Transparency is praised. Vulnerability is encouraged. Openness is celebrated. And yet, experienced leaders learn something quietly. You cannot share every doubt you have without destabilizing the people around you. 🧠 Why this feels uncomfortable at first Early leadership teaches you to be open. Say what you’re thinking. Invite discussion. Show humanity. That works, until the scope of responsibility changes. At senior levels, your doubts don’t land as thoughts. They land as signals. Research on authority and emotional contagion reveals that leaders’ uncertainty amplifies anxiety in teams, even when communicated with good intent. What feels like honesty to you can feel like instability to others. 👀 How this shows up in leadership You notice it when: • a casual concern turns into team panic • a tentative thought becomes a rumor • a passing doubt reshapes priorities • people wait for reassurance instead of acting You didn’t change direction. But the system did. Because leadership presence magnifies everything. 😂 The funny part leaders recognize Every experienced leader has said this sentence internally: “I probably shouldn’t have said that out loud.” Not because it was wrong. But because it traveled further than intended. Words weigh more when they come from the top. Even the quiet ones. ⚠️ The danger of radical transparency Total transparency sounds noble. In practice, it can be destabilizing. Research in organizational psychology shows that people look to leaders for orientation under uncertainty, not for raw processing. Leaders who externalize every doubt force teams to carry emotional weight they’re not positioned to hold. That’s not empowerment. It’s offloading. 🏗️ What strong leaders learn to do Strong leaders don’t suppress doubt. They contain it. They: • process uncertainty with peers, not subordinates • share conclusions, not every internal step • name risk without dramatizing it • provide direction even when they’re still thinking They understand something critical. Leadership isn’t about being certain. It’s about being stabilizing. 🔍 The leadership reframe The question isn’t: “Am I being honest?” It’s: “Is this helpful for the people hearing it?” You can be authentic without being unfiltered. You can be human without being destabilizing. You can hold doubt without passing it on. That’s not hiding. That’s leadership maturity. Because your job isn’t to broadcast every internal struggle. It’s to absorb uncertainty, decide responsibly, and give others enough steadiness to do their best work while you carry the rest. And yes, it’s brutally hard some days. #Leadership #Executiveleadership #CEO #Decisionmaking #Management #Leadershipdevelopment #Business #Leadershiplessons

Transparency isn’t what you say. It’s what you show. Telling your team “we value transparency” means nothing if your decisions stay behind closed doors. Transparency isn’t a slogan, it’s a practice. And it starts with leadership. Here are 3 ways to build true transparency inside your team: 1. Share the “why,” not just the “what.” Don’t just announce decisions. Explain the reasoning. It helps your team understand trade-offs and makes them feel included. 2. Open up decision-making. Invite input before locking things in. People are far more invested in choices they’ve contributed to. 3. Be upfront about challenges. Don’t hide bad news or tough calls. Teams respect leaders who admit problems and work through them together. When transparency is lived, not just spoken: Trust goes up. Rumors go down. Alignment becomes effortless. Your culture isn’t defined by posters on the wall. It’s defined by what your team sees you do when the doors should be open.

I thought sharing the company’s cash flow showed transparency, until my team said it felt like watching their parents panic about money. In 2023, like many tech companies, we faced tough financial decisions. I believed the best way to build trust during uncertainty was to put everything on the table. During town halls, I openly shared balance sheets, cash flow, and even our exact bank balances. After one meeting, a respected colleague approached me privately and said, “Janine, I appreciate what you're trying to do, but this is too much information. I don’t need to see every detail—it just makes me anxious.” That feedback completely shifted my thinking. Transparency is essential, but it isn’t about showing every detail. It's about carefully choosing what to share, ensuring your team feels informed and empowered, not overwhelmed. Think of how parents handle tough financial times: They acknowledge challenges honestly, but don’t burden their kids with specifics beyond their control. They create stability and confidence, even if they're still figuring things out behind the scenes. As leaders, our role is similar: • Be honest about challenges without oversharing details that don’t help. • Provide context that's actionable and relevant. • Filter out information that causes unnecessary anxiety or confusion. • Communicate clearly and confidently about the path ahead. Trust isn't built by revealing everything. It's built through steady guidance, thoughtful transparency, and consistently keeping your word. I learned that the most effective transparency isn't about how much information you share, but choosing the right information to help your team move forward confidently. I'd welcome hearing from others who've navigated this balance between transparency and over-sharing.

Most companies/ teams say they want to move fast. Very few build the discipline to actually do it. One thing I have learned is that speed without structure always collapses. Teams either get slowed down by approvals or ship things leaders have no visibility into. At my previous org, we solved this by creating a simple rule. Teams can ship to an early access tier anytime. General availability requires proof, not opinions. The surprising part is how many customers want to live on the frontier. Almost ten percent opted into early access. That was thousands of businesses giving us real-world signals every single day. To ship something to the full customer base, teams had to answer a clear review template: 1. What was built and what problem it solves. 2. A short demo the team can explain in under three minutes. 3. Did the early access data meet the goals. 4. What customers actually said based on support tickets, surveys, and call transcripts. 5. Whether the feature is easy to find and use for a first time customer. 6. If sales, customer success, and support teams are fully ready. 7. The rollout plan including pricing, communication, and onboarding. It sounds heavy, but it is actually liberating. Everything is documented. Quality is visible. Leaders do not micromanage because the process already creates accountability. The best part is that most of this became automated using AI connected to our product systems, CRM, analytics, and support tools. Teams spent their time building instead of chasing paperwork. Leaders had forty eight hours to review. If they missed it, the feature shipped. The responsibility shifted where it belongs. Teams owned the outcome. Leaders focused on clarity, not bottlenecks. It turned out to be the simplest way to maintain speed with confidence. Empowerment with guardrails. Innovation with transparency. Quality without slowing down. If you want both pace and trust inside an engineering org, create a system where teams can run and leaders can still sleep at night. Would you adopt a workflow like this in your org?

I’ll never understand the engineering leaders who think it’s a good idea to hide productivity efforts from individual software engineers. It exhibits a dangerous lack of trust that is highly likely to be counterproductive. Why? 🧠 Engineers are smart. They’ll figure out you're measuring something, and the secrecy will breed distrust and resistance. 💡 Your engineers have the best insights into what's slowing them down. By hiding your intentions, you're missing out on valuable perspective. 🙏 The most successful productivity initiatives are collaborative. When engineers feel ownership over improvements, they're more likely to embrace and champion changes. 👓 Transparency builds trust. Being open about your goals — shipping faster, reducing toil, improving developer experience — creates allies instead of skeptics. 📈 The best engineering organizations make productivity data accessible to everyone. They use it to drive improvements, not performance reviews. If you're afraid to acknowledge that you’re examining productivity, you’re likely to arrive at the wrong answers about how to improve it.