Luke Dodge Blog RSS Feed

How Halloween teaches us good teamwork

Thu, 29 Oct 2026 00:00:00 GMT

Trick-or-treating works because a neighborhood agrees to participate.

Some people put on costumes and go door to door. Others turn on their porch lights and get a bowl of candy ready. Each side puts in effort, and together they create something neither could make happen alone.

I’ve been thinking about how much workplace collaboration depends on that same exchange. We ask people to speak up, seek advice, and reach across teams. But those actions only work when someone on the other side is ready to welcome them.

You have to be willing to knock

If you want candy on Halloween, you have to leave the house. You have to walk up to a door, knock, and ask.

Asking for help at work can feel surprisingly similar.

You might need a colleague’s perspective, an introduction, or someone to explain a process you don’t understand. Before you get any of those things, you have to make your need visible.

That can be uncomfortable. Asking means admitting you don’t have every answer. It means interrupting someone, risking a rejection, or wondering whether you should have figured it out yourself.

It’s easy to let that discomfort make the decision for you. You keep working alone, spend another afternoon trying to solve the same problem, or wait for someone to notice that you’re stuck.

Sometimes independent effort is exactly what a situation needs. But when another person’s knowledge would help you move forward, staying silent has a cost too.

A useful request doesn’t need to be elaborate. Explain what you’re trying to accomplish, what you’ve already tried, and where you could use help. Give the other person a clear way to contribute.

You don’t have to feel completely comfortable before you knock.

People need a reason to approach your door

The other half of the exchange is just as important.

On Halloween, a dark porch sends a clear signal. Most people won’t walk up to a house with the lights off and no sign that anyone is home.

At work, our signals can be harder to recognize—especially our own.

We may say, “My door is always open,” while reacting to questions with impatience. We may encourage people to ask for help, then make them feel embarrassed for needing it. We may invite collaboration but rarely make time for the conversations it requires.

Over time, people learn which signal to trust.

Being approachable takes more than announcing your availability. It shows up in how you respond when someone actually approaches you.

Do you listen before assuming they should know the answer? Can you explain something without making the person feel small? If you’re busy, do you offer a realistic time to reconnect?

You don’t need to be available every minute. A clear, considerate boundary can make asking easier: “I can’t give this my attention right now, but I have fifteen minutes tomorrow morning.”

That gives someone a path forward—and a reason to come back.

Be ready when someone shows up

Turning on the porch light is an invitation. Having candy ready is how you follow through.

The workplace equivalent is giving a request some genuine attention. That might mean sharing your experience, asking a question that helps someone think, or connecting them with the right person.

You won’t always have the answer. You can still help someone find their next step.

What matters is whether the experience reinforces the invitation. When someone takes the risk of asking, your response helps determine whether they’ll do it again.

Make the next conversation easier

Most of us spend time on both sides of the door. We need help in one area and have something to offer in another.

That gives us two ways to improve collaboration: make a clear request when we need support, and respond thoughtfully when someone asks us.

Neither guarantees a perfect exchange. But each makes the next conversation a little easier.

A neighborhood comes alive on Halloween through lots of small acts of participation. A team builds trust much the same way: one person knocks, another welcomes them, and both have a reason to keep showing up.

Curiosity is an effective form of urgency

Wed, 09 Sep 2026 00:00:00 GMT

Curiosity is a form of urgency.

It gives us a reason to move before we're forced to. It's easy to keep digging when something is obviously broken. It's harder when everything seems fine.

That's usually where we stop.

But "everything seems fine" isn't a very interesting place for a story to end. There's often more lurking beneath the surface for the people willing to ask one more question:

What if there's a deeper problem to solve?
What if I'm not actually blocked?
What if there's another alternative?
What if "good enough" is hiding something better?

The difference isn't necessarily working harder. It's being curious enough to keep pulling the thread.

When 'Good Enough' Becomes the End of the Story

In engineering, we spend a lot of time solving problems. We investigate failures, remove blockers, improve processes, and make decisions with incomplete information.

But there's an important distinction between solving the problem in front of us and understanding whether it's the right problem to solve.

A system might be working exactly as designed, but that doesn't mean it's serving its users well. A team might be consistently delivering work, but that doesn't mean they're working on the most valuable things. A process might have existed for years without anyone remembering why it was created in the first place.

None of these situations necessarily creates urgency. There's no incident to resolve, deadline to meet, or obvious failure demanding attention.

And that's precisely why they're easy to overlook.

We tend to treat urgency as something imposed on us by circumstances. Something breaks, someone complains, or a deadline approaches, and suddenly we have a reason to act.

Curiosity works in the opposite direction. It creates a reason to investigate before the consequences demand it.

Not every question needs to become a project, and not every working system needs to be reinvented. The point isn't to challenge everything indiscriminately. It's to recognize that the absence of an obvious problem isn't proof that there's nothing left to discover.

The Stories We Don't Tell

Stories are full of people who don't pull that thread.

Which brings me, naturally, to Bilbo Baggins.

Bilbo had a mysterious magic ring for 60 years.

Sixty years!

And for most of that time, it was just a particularly useful magic ring. Imagine being a little more curious about that.

Where did this thing come from? Why does it make me invisible? Why am I getting weirdly attached to it? Is it perhaps concerning that I won it from a cave-dwelling former hobbit who called it his "precious"?

There's a version of The Lord of the Rings where someone starts asking those questions a little earlier.

It would be a much worse trilogy. But probably a much better outcome for Middle-earth.

Of course, Bilbo wasn't entirely oblivious, and Gandalf had his suspicions. The point isn't that nobody ever questioned the Ring. It's how easily something extraordinary can become ordinary when we live with it long enough.

We accept things because they've always been that way. The longer they remain familiar, the less likely we are to question them.

Until something happens that makes ignoring them impossible.

That's a wonderful way to create conflict in a story. It's a considerably less appealing way to run an engineering organization.

Don't Wait for the Call to Adventure

One of the things I find fascinating about storytelling is how often a character's journey begins with a disruption to their ordinary world.

Something happens that forces them to act. A problem appears, a stranger arrives, or an unexpected responsibility falls into their lap.

But what if they didn't wait?

What if they started asking questions before the world demanded answers?

There's a useful distinction here for anyone responsible for leading people or solving complex problems. We can spend our time responding to the challenges that find us, or we can develop the curiosity to discover opportunities and problems before they become unavoidable.

That doesn't require treating everything as an emergency. In fact, curiosity is often most valuable when we have enough breathing room to explore without the pressure of an immediate crisis.

Sometimes the most useful thing a leader can do is ask a question nobody else thought was worth asking.

What are we assuming is true? Why do we do it this way? What would we try if this constraint didn't exist? What happens if we follow this idea one step further?

These questions won't always produce something useful. Sometimes the answer really is that everything is fine.

But occasionally, one more question changes how we understand the entire problem.

We tend to wait for the problem to become urgent before we start questioning it.

Curiosity lets us get there first.

You don't always need to wait for the call to adventure. Sometimes you can go looking for it yourself.

Otherwise you're going to leave your poor nephew traumatized and missing a finger.

Knowing how to pause is your competitive advantage

Wed, 01 Jul 2026 00:00:00 GMT

The more I work with AI as an engineering manager, the more I find one skill has become dramatically more valuable: the deliberate pause.

I know that might sound backwards. We're surrounded by tools that let us build faster, write faster, analyze faster, and ship faster. With each new advancement, the expectation seems to be that we should be producing more in less time. It feels like the people moving the quickest must be winning.

But AI hasn't eliminated the biggest bottleneck. It's just made it easier to reach it.

Us.

The hardest part of most work isn't implementation anymore. It's deciding what deserves to be implemented in the first place.

AI can help you build a feature in half the time, but it can't reliably tell you whether it's the right feature. It can generate a beautiful report in minutes, but it can't tell you whether anyone should have asked for that report.

We've made tremendous progress in how quickly we can produce things. I'm not convinced we've made the same progress in deciding what we should produce.

When Generation Becomes a Distraction

One of the traps I've started noticing is how easily we confuse generation with progress.

One of AI's greatest strengths is making exploration incredibly cheap. That's a good thing! If my team can explore 50 potential solutions in the time it used to take us to explore five, I'll happily take that trade.

But there's a cost we don't always account for.

Every solution we generate is another solution competing for our attention. Someone still needs to understand what was produced, evaluate whether it solves the problem, and decide what to do with it.

If 45 of those solutions were never worth considering in the first place, we've also created 45 distractions. We've made the search harder.

This becomes especially important when working on a team. Generating something doesn't mean it's ready to be used. Someone else may need to review it, maintain it, or build on top of it. The time we save during implementation can easily become time someone else spends figuring out what we've created.

That's not an argument against using AI to explore more possibilities. Exploration is valuable, and being able to discard an unsuccessful approach quickly is a tremendous advantage.

The problem comes when we treat the number of things we've produced as evidence of how much progress we've made.

Bringing Back the Deliberate Pause

This is why I keep coming back to David Marquet's idea of the deliberate action and it's use of a mandatory pause.

There's an important distinction between pausing and slowing down. We tend to associate slow with failure. If something isn't moving quickly, we assume there's a problem. But a pause isn't an absence of progress. It's an intentional moment to make sure we're heading in the right direction.

In engineering, we're familiar with the cost of making the wrong decision. A feature that solves the wrong problem doesn't become valuable just because we delivered it ahead of schedule. An implementation that creates unnecessary complexity doesn't become easier to maintain because it took less time to write.

The deliberate pause creates an opportunity to ask a few questions before committing our energy:

What problem are we actually trying to solve? It's easy to jump into a solution before we've fully understood the problem. AI makes that temptation even stronger because we can start generating something almost immediately.
Is this the highest-leverage thing we could be working on? Just because something is easy to produce doesn't mean it's worth producing. We still have to decide where our attention will make the biggest difference.
What would success actually look like? Without a clear definition of success, it's difficult to distinguish a useful result from something that merely looks finished.

These aren't complicated questions. They're questions we already know we should be asking. The challenge is remembering to ask them when the tools make it so easy to skip ahead.

Five minutes of thinking can save hours of implementation.

Consistency Builds Trust

Ironically, AI makes that pause even more valuable.

When implementation was expensive, thinking was naturally built into the process. You had time while you were writing code, creating documents, or building presentations to reconsider what you were doing. That didn't guarantee good decisions, but the work itself created opportunities to reflect.

Now implementation is almost free.

Good judgment isn't.

As an engineering manager, I'm less interested in how many things someone can produce than in whether I can consistently trust the results of their work.

That doesn't mean speed isn't important. Delivering quickly matters, and someone who takes forever to make a decision isn't necessarily exercising better judgment. There's a balance between moving quickly and making sure the work is worth doing.

But consistency is what builds trust over time.

When someone consistently delivers useful work, the people around them learn they can depend on it. They spend less time second-guessing decisions, questioning whether something is ready, or worrying about what they'll discover later.

That trust makes teams more effective. It also makes you the person others want to work with when something really important needs to get done.

I suspect the engineers who stand out over the next few years won't necessarily be the ones producing the most output. They'll be the ones who can consistently turn these increasingly powerful tools into useful outcomes.

Finding the Needle

AI has made it incredibly easy to create haystacks.

We can generate more code, more documents, more solutions, and more possibilities than ever before. And there's genuine value in that. Being able to explore more options without investing enormous amounts of time is an opportunity we shouldn't ignore.

But quantity alone doesn't guarantee we're getting closer to what matters.

If our goal is finding needles, creating more hay isn't automatically progress. At some point, we have to stop adding to the pile and consider whether we're looking in the right place.

That's where the deliberate pause earns its value. Not by replacing speed, but by making sure that speed is taking us somewhere worth going.

The goal was never the haystack.

It was always the needle.

Nobody knows what they're doing with AI yet (and that's okay)

Wed, 29 Apr 2026 00:00:00 GMT

As an engineering manager, I spend a lot of time talking about AI. Mostly answering questions.

What's the best way to use it? What does "good" use of AI actually look like? How do I keep improving while everyone around me is moving faster? Does everything I've learned still matter? What should I even be learning now?

The questions never stop.

If you're in any kind of leadership role, you're probably getting the same ones. And you're expected to have answers. Not just for yourself, but for the people looking to you for direction. That's part of leadership, after all. Helping people navigate uncertainty and figure out what to do next.

But there's a problem with that expectation.

I'll let you in on a little secret:

No one knows the answers yet.

You'd think this master's degree in machine learning would make this easier. It doesn't.

I understand how these systems work, at least more than the average person. But understanding the technology and knowing how it's going to change the way we work are two very different things. I can explain how a neural network learns, but that doesn't mean I know what software engineering is going to look like five years from now.

And I'm increasingly convinced that nobody else does either.

We're Still Figuring Out the Fundamentals

We're in the middle of one of the most disruptive shifts our industry has seen, in a field that's barely had time to settle before changing again.

Modern software engineering, depending on how you count it, is what, 50 to 70 years old? Compare that to medicine, with thousands of years of history and a few hundred years of increasingly rigorous scientific practice. Or architecture, where people have been designing and constructing buildings for thousands of years.

Those fields have had generations to build foundations. To test, fail, refine, and stabilize. They still change, sometimes dramatically, but they have a substantial body of accumulated knowledge to build upon.

In software, we're still arguing about the fundamentals.

Think about how much software development has changed in just the last twenty years. We've gone from debating whether agile development was a good idea to arguing about which version of agile we're doing wrong. We've moved from physical servers to the cloud, from monoliths to microservices (and sometimes back again), and from writing every line of code ourselves to asking an AI to write entire features.

And through all of that, we're still figuring out what good software engineering actually looks like.

Now we're introducing technology that challenges some of our most basic assumptions about how software gets built.

Of course we don't have all the answers.

The Ground Is Actually Moving

So if you feel behind, or unsure, or like the ground keeps moving under you, that's not in your head. The ground is actually moving. It's changing constantly. Of course it's hard to feel stable right now.

What's considered effective today might be outdated six months from now. Tools are improving faster than most organizations can adopt them, and we're being asked to make decisions about technology whose capabilities and limitations are still changing.

There's also a strange pressure that comes from watching everyone else experiment in public. Every day, someone seems to have discovered a new workflow that's going to revolutionize software development. Another person claims they've stopped writing code entirely. Someone else insists that engineers who aren't using AI for everything are already falling behind.

Maybe they're right about some of it. Maybe they aren't.

The problem is that we're often comparing our own uncertainty to everyone else's confidence. And confidence isn't necessarily evidence that someone has figured things out.

It's tempting to look for someone who has the answers, especially when you're responsible for helping other people find their way. But I think we'd be better served by getting comfortable with the idea that those answers don't exist yet.

At least not in any permanent sense.

Remember the Science Part

We forget sometimes that it's called computer "science." Not computer "we already know the answer."

So embrace the uncertainty! This is the moment to lean into experimentation, not fear.

And I don't mean experimenting just for the sake of trying every new tool that comes along. That's an easy trap to fall into, especially when there's a new AI product promising to change everything every other week.

I mean approaching the problem with an experimental mindset.

Form a hypothesis. Try something. See what works. See what breaks. Adjust and repeat.

Maybe you think AI can help your team write better tests. Great. Try it on a few different types of problems and see what happens. Are the tests actually better? Are they easier to maintain? Does it save time once you account for reviewing and correcting the results?

Maybe you're wondering whether AI makes junior engineers more productive or whether it prevents them from developing the skills they'll need later. That's a much harder question, but it's still something worth exploring rather than assuming you know the answer.

The important part is being willing to challenge your assumptions, including the ones that seem obvious.

Some experiments will work. Others won't. Some things that work today might stop working as the technology changes. That's fine. The goal isn't to find the perfect workflow that will carry us through the next decade. It's to keep learning enough to make better decisions as we go.

Progress Matters More Than Certainty

I think this is especially important for people in leadership roles.

We're used to being the ones who provide direction. People come to us with problems, and we're supposed to help them find solutions. It can be uncomfortable to admit that we don't know what the right answer is.

But I don't think our job is to pretend we know.

Our job is to help create an environment where people can figure things out. Where trying something new doesn't require being certain it will work. Where we can share what we're learning, acknowledge what isn't working, and change direction when we discover something better.

That doesn't mean abandoning standards or chasing every new technology. It means being deliberate about what we're trying to learn and honest about what we actually know.

We're all figuring this out together, whether we admit it or not.

As long as you're moving in a positive direction, learning from what works and what doesn't, I think you're doing pretty well.

Progress matters more than certainty right now.

And if you do figure it all out, let me know. I have a few questions.

Your first 90 days are about trust, not productivity

Wed, 20 Aug 2025 00:00:00 GMT

The first 90 days at a new company are a brutal learning curve.

You're learning new systems, names, acronyms, team dynamics, priorities, and unspoken rules, all while trying not to break anything in the process. Even when you're experienced in your role, you're still starting from scratch in a lot of ways.

It's easy to fall into the trap of chasing impact early. You want to prove your worth, make a splash, and show everyone they made the right hire. There's an unspoken pressure to hit the ground running, even when you're still figuring out which direction to run.

I've made that mistake before.

When you're running instead of walking, it's easy to step on toes, especially when you don't yet know who's in the room or how the room even works. You might make some quick improvements, but you're just as likely to overlook important context, solve the wrong problem, or unintentionally undermine relationships you're only beginning to build.

What helped me shift my perspective was realizing something that seems counterintuitive:

Your job in the first 90 days isn't to deliver. It's to build trust.

With your manager, your team, your peers, and your cross-functional partners. Everyone you'll depend on to be successful in your new role.

That doesn't mean sitting around waiting to understand everything before taking action. Building trust is hard work. It requires showing up, asking good questions, getting curious about why things work the way they do, admitting when you don't know something, and following through on what you say you'll do.

It also means resisting the temptation to immediately fix everything you notice.

Every organization has decisions that seem strange from the outside. Sometimes they're the result of constraints you haven't discovered yet. Sometimes they're compromises made by people who were solving a different problem. And sometimes they're genuinely opportunities for improvement.

The challenge is knowing the difference.

That's where relationships become so important. The more you understand the people around you, the more context you gain about the work itself. You begin to understand what matters, where the friction exists, and which problems are worth solving first.

And when you've built trust, people are more willing to share what they actually think, challenge your assumptions, and support the changes you eventually make.

None of this means you won't accomplish anything in your first 90 days. You'll still make decisions, solve problems, and contribute to the team. But those outcomes become a natural result of learning and building relationships rather than a desperate attempt to prove you belong.

I think that's the hardest part of starting somewhere new. Accepting that you don't have to demonstrate your full value immediately, even when that little voice in your head insists otherwise.

And the irony? When you focus on trust, you end up making a bigger impact anyway.

How to identify successful vs. high-performing teams

Fri, 26 Jan 2024 00:00:00 GMT

It's crucial to recognize that not all successful teams are inherently high-performing. While success revolves around meeting user needs and achieving project completion, high performance extends further, emphasizing efficiency, quality, and timely delivery. It's imperative for long-term growth to foster teams that are not just successful but also high-performing.

Identifying Success and High-Performance

This distinction between successful and high-performing teams is crucial for recognizing the unique challenges and characteristics of each team type. Let's explore examples highlighting the difference between successful and high-performing teams.

Project Completion

Successful Teams: Prioritize delivering projects up to the Minimum Viable Product (MVP), often falling short of exceeding ambitious project goals. Their emphasis may lead to compromises in terms of quality and efficiency.
High-Performing Teams: Not only complete projects but excel in exceeding project goals with a focus on quality and efficiency. Their commitment goes beyond minimal requirements, ensuring outstanding outcomes for every project.

Adaptability

Successful Teams: Exhibit a degree of adaptability to changing project requirements and user needs, but may struggle with proactively embracing innovation.
High-Performing Teams: Embrace a proactive stance toward innovation, continuously adapting and introducing improvements to stay ahead. Their adaptability extends beyond the basics, incorporating a forward-thinking approach to anticipate and meet future challenges.

Leadership

Successful Teams: Leaders guide the team toward project completion, but their effectiveness may be limited to task-oriented directives.
High-Performing Teams: Demonstrate strong leadership that not only directs but inspires and empowers team members, fostering a culture of excellence. This leadership style encourages innovation and proactive contributions from every team member.

Communication

Successful Teams: Emphasize effective collaboration to meet project goals, but communication may lack the depth and transparency required for optimal understanding among team members. This can lead to potential misunderstandings and inefficiencies in project execution.
High-Performing Teams: Foster clear, open, and dynamic communication channels, ensuring efficient information flow among team members. Their proactive communication approach contributes to a cohesive team environment, reducing the likelihood of misunderstandings and enhancing overall efficiency.

Feedback and Continuous Improvement

Successful Teams: Gather user feedback for feature enhancements, but the commitment to continuous improvement may lack depth. Internal and external feedback may not be systematically sought, potentially leading to missed opportunities for refining processes and outcomes.
High-Performing Teams: Embrace a robust culture of continuous improvement, actively seeking and incorporating both internal and external feedback. This systematic approach ensures ongoing refinement of processes and outcomes, contributing to sustained excellence and adaptability.

Risk Management

Successful Teams: Manage risks to ensure project completion within established parameters, but the approach may be reactive rather than proactive. This reactive stance may result in challenges in handling unforeseen issues, potentially causing disruptions to timelines and project quality.
High-Performing Teams: Proactively identify and mitigate risks, demonstrating a robust risk management strategy. Their forward-thinking approach minimizes potential disruptions, showcasing a commitment to maintaining both timelines and the quality of project deliverables.

Client Satisfaction

Successful Teams: Primarily focus on delivering a product that satisfies user and stakeholder requirements, but the emphasis may fall short of creating exceptional client experiences. This approach may result in meeting expectations without consistently exceeding them, potentially hindering the development of lasting relationships.
High-Performing Teams: Go beyond mere satisfaction, actively aiming for exceptional client experiences. By consistently exceeding expectations, they meet and surpass client needs, fostering long-lasting and meaningful relationships built on trust and outstanding service.

Metrics and KPIs

Successful Teams: Track project milestones and completion metrics, but the scope of their metrics may be limited. They may focus on basic project metrics without delving into a more comprehensive set, potentially missing out on valuable insights related to code quality, delivery times, team efficiency, and other relevant performance indicators.
High-Performing Teams: Demonstrate a commitment to excellence by utilizing a comprehensive set of KPIs. Their metrics span beyond project milestones, encompassing code quality, delivery times, team efficiency measures, and various other relevant indicators. This broader approach provides a more holistic view, facilitating strategic decision-making and continual improvement.

Employee Satisfaction and Retention

Successful Teams: Strive to maintain a positive work environment to retain team members, but the effort may fall short of significantly impacting turnover rates. While the environment remains generally positive, challenges in consistently fostering higher engagement and cohesive motivation among team members may hinder the achievement of optimal retention levels.
High-Performing Teams: Stand out by actively prioritizing employee satisfaction, resulting in significantly lower turnover rates, heightened engagement, and a more cohesive and motivated workforce. Their commitment to fostering a positive workplace culture contributes to building enduring relationships with team members.

Strategic Alignment

Successful Teams: Strive to align with overall business goals to contribute to the company's success, but the alignment may be more surface-level. While efforts are made to support broader objectives, the understanding and depth of alignment with long-term organizational objectives may need to be improved.
High-Performing Teams: Elevate strategic alignment by ensuring a deep understanding of the business strategy. They actively align projects with long-term organizational objectives, positioning themselves as strategic assets that contribute meaningfully to the company's overarching success. This comprehensive alignment sets the stage for sustained excellence and innovation.

In Conclusion

Distinguishing between the qualities of successful and high-performing teams is paramount for fostering a culture of excellence. Recognizing the unique characteristics and potential pitfalls of each set of attributes allows organizations to strategically navigate challenges and capitalize on strengths.

Yet, as the distinction unfolds, it becomes clear that being a high-performing team demands a more intricate and proactive approach. While the path to high performance is more challenging, success should always take precedence over performance. As teams strive for excellence, it becomes evident that achieving success is an essential precursor to high performance.

Ultimately, the journey toward building exceptional software engineering teams involves a strategic focus on success, a nuanced understanding of the success-performance relationship, caution against overemphasis, and awareness of potential pitfalls. In this intricate dance, success paves the way for high performance, creating a sustainable and innovative environment that propels teams toward continuous refinement and excellence.

There is great power in a descriptive project name

Fri, 29 Dec 2023 00:00:00 GMT

Where efficiency and clarity reign supreme, the choice of project names plays a crucial role. While version numbering remains a steadfast practice, this discussion delves into the advantages of steering clear of the generic "Notifications Version 3" or "Home Screen Phase 2" approach. Let's explore why embracing descriptive titles can revolutionize conceptualizing, communicating, and executing projects.

Setting Expectations and Defining Goals

Traditional numerical titles, though functional in their own right, often fall short of providing a clear understanding of a project's essence. Descriptive titles, on the other hand, immediately set expectations and define goals. Imagine trying to decipher the contents of "Notifications V3" - a seemingly endless saga with no apparent conclusion. Contrast that with the crisp and purposeful "Update Signup Form," which not only describes the focus but also establishes a shared expectation for success.

Creating Boundaries and Managing Scope

One of the challenges with numerical titles is their potential to become an indefinite catchall. The absence of a defined scope can lead to scope creep, as the project's purpose remains vague. Descriptive titles act as project boundaries, offering a clear delineation of what falls within the project's purview. For instance, "Billing Payment Methods Update" underlines a specific focus, making deviations more noticeable and subject to scrutiny.

Clarity in Codebase Management

In the labyrinth of a growing codebase, the importance of clarity cannot be overstated. Numerical versions may leave you guessing about the relevance of a particular feature or component. A component named "NotificationsV2" may beg the question: Is there a V3 or a V9? Descriptive titles eliminate the need for such exhaustive context by standing alone. They offer a snapshot of a feature's status, making it clear whether it is current or outdated, without requiring a deep dive into the entire system.

Simplifying Cleanup Efforts

The aftermath of a project often involves cleaning up outdated code. Numerically titled projects can complicate this process, demanding meticulous renaming or deletion efforts. In contrast, a well-named project, flagged as deprecated or legacy from the outset, streamlines the cleanup process. No more scrambling to decipher which version is current or what should be deleted – a simple removal of the marked legacy code concludes the project seamlessly.

Conclusion

While version numbering remains a crucial aspect of project management, the benefits of adopting descriptive project names are undeniable. They set expectations, create boundaries, enhance communication, and simplify cleanup efforts. So, before diving into the next project, consider the power of a name – one that tells a story, defines a purpose, and stands the test of time. After all, in project management, a well-chosen name can be the key to success.

Documentation is the cornerstone of alignment

Thu, 07 Dec 2023 00:00:00 GMT

Effective communication is the bedrock upon which successful teams are built. The ability of a team to align, collaborate, and execute depends heavily on the clarity and accessibility of information.

The Power of Putting Pen to Paper

At first glance, jotting down decisions and processes may appear labor-intensive, raising doubts about its future benefits. However, the act of documentation goes beyond mere historical record-keeping. Its primary advantage lies in nurturing enhanced alignment and understanding among team members.

By transforming abstract thoughts into tangible, shareable entities, documentation plays a crucial role in creating a common ground. A shared text helps eradicate ambiguity and reveals gaps in comprehension. This newfound clarity becomes a central focal point for agreement, fostering alignment within the team. With a documented foundation, teams can seamlessly direct their energy, preventing inadvertent divergence.

Whether it’s code documentation, architecture diagrams, or project specifications, written communication is a vital starting point for cultivating a shared understanding. It encapsulates processes, workflows, and decisions, providing team members with a reference point to comprehend the project’s intricate landscape.

An Evolving Lifeline

Unlike verbal exchanges that fade and shift with time, documentation offers persistence and an unchanging record. This quality makes it a valuable asset for revisiting decisions, understanding historical context, and streamlining the onboarding process for new team members. In contrast, relying on memory alone can be unreliable and subject to forgetfulness and distortions.

Consider it as a stable thread of consistency extending beyond the initial moment of team alignment, akin to a guiding rope in a blizzard. However, it's crucial to recognize that this stability doesn't imply a static nature for documentation.

To achieve optimal effectiveness, one should treat documentation as a living entity that adapts to the project's evolution and reflects its current state. Outdated or unclear documentation introduces risks such as confusion and misalignment, which can ultimately lead to collaboration breakdowns. To avoid these pitfalls, regular reviews, updates, and feedback loops are indispensable in keeping documentation in sync with the project’s dynamic nature.

Recognizing the Gaps: Documentation Alone Isn't Always Enough

While documentation is a powerful catalyst for team alignment, it's imperative to recognize its limitations. Understanding does not automatically translate to alignment, and the mere act of writing something down doesn't guarantee results.

Misalignment may stem from factors beyond the absence of documentation. Team dynamics, communication styles, and varying levels of expertise can also contribute to challenges in alignment.

To address these complexities, teams must adopt a holistic approach. Regular communication, both written and verbal, fosters an environment where team members feel comfortable seeking clarification, sharing insights, and collaborating on problem-solving. Documentation should complement these interactions, providing a structured framework that supports, rather than replaces, human communication.

Conclusion: A Balancing Act

There's no magic inherent in the documentation that transforms a project. For instance, an exhaustive best practices document only holds value if accompanied by a robust code review process. Documentation is a tool, not a solution unto itself.

While documentation is a cornerstone of team alignment, providing structure, clarity, and a shared reference point, it is not a silver bullet. To maximize its effectiveness, teams must balance written communication with other forms of interaction, recognize the importance of quality documentation, and ensure that information is easily accessible to all team members.

Documentation is a powerful ally in pursuing team alignment, but its true potential is realized when coupled with a culture of open communication, continuous improvement, and a shared commitment to project success.

Define your team's success to always win

Mon, 20 Nov 2023 00:00:00 GMT

Crunch time. We’ve all been there, but everything is wrong. You can feel your goals slipping further and further away every day. It seems inevitable you’ll be missing your targets. The feeling among the team is palpable. These moments have a long-lasting negative impact on team morale and future performance.

An “off-plan” project in software engineering typically refers to a project that has deviated from its original or established plan. It describes a project that is not proceeding according to the initially defined scope, timeline, or other key parameters outlined during the planning phase.

There are numerous reasons why a project might go off-plan. It could be due to changing requirements, unexpected technical challenges, resource constraints, or other unforeseen issues. Managing an off-plan project requires adaptability and effective communication. It often involves making adjustments to the project plan to bring it back on track or to align it with new circumstances. Follow these steps to turn an off-plan project into a success.

1. Identify Project Variables

Projects have a variable that is movable. The original iron triangle project management, proposed by Dr. Martin Barnes in 1969, identifies three project variables: time, scope, and resources. Scope refers to project requirements, time is the deadline for the project, and resources are the people and supplies/materials available for use.

The resources on most teams are fixed (people) or straightforward to request (supplies/materials), so we’ll assume your resources are fixed for this discussion. Bringing people onto a project is doable and might help, but it’s the trickiest variable to adjust because it changes the team dynamic. We’ll cover how to do this in another article.

To ensure your team is successful, you need to understand which variable applies to your project. There are shades of gray and you may have wiggle room in both time and scope, but one will be significantly more flexible.

Let’s break down each type of project with different sets of constraints and how to identify them:

Fixed Scope, Variable Time

Constraints: The project has a defined scope that should not change, but the time for completion is flexible.
Identification: Look for projects where specific deliverables or features are well-established, but the timeline is subject to adjustments based on various factors. Development methodologies like Scrum use this model (i.e. MVP).

Fixed Time, Variable Scope

Constraints: There is a fixed timeframe for project completion, but the set of features or deliverables is adjustable.
Identification: Identify projects with strict deadlines or release dates where the features or deliverables can be adapted to fit within time constraints. Development methodologies like Basecamp’s “Shape Up” use this model (i.e. appetite).

Variable Time, Variable Scope

Constraints: Both the project’s scope and the timeline are flexible.
Identification: These projects are characterized by evolving requirements and timelines. Regular adjustments and collaboration with stakeholders are common.

These might seem like dream projects, but they are also at a high risk of failure. Ambiguous goals lead to ambiguous success, but failure is always specific.

Fixed Time, Fixed Scope

Constraints: Both the project scope and timeframe are predetermined and cannot change.
Identification: Projects with clearly defined features and a strict deadline fall into this category. Adherence to a fixed plan is required.

Identifying the project type requires a thorough understanding of project requirements, timelines, and flexibility within the given constraints. Regular communication with stakeholders and a comprehensive project planning phase can help you accurately categorize the project type.

2. Adjust Expectations

Understanding your project’s variable is crucial, as it provides room for negotiation on behalf of your team. Committing to the fixed aspects while strategically adjusting what is variable allows you to steer your team back on course. Let’s explore how to do this with each type of project.

Fixed Scope, Variable Time

For projects with fixed scope but variable time, effective communication becomes paramount to addressing delays. Openly discuss with stakeholders the possibility of extending the estimated time. Transparency is key; inform stakeholders that the extension aims to enhance the project’s quality and ability to deliver on requirements. The earlier you communicate such adjustments, the better, as surprises in time deviations can negatively impact project dynamics. Estimates are crucial to build trust in the adjustments.

Fixed Time, Variable Scope

For projects with fixed time but with a variable scope, the focus shifts to adapting the project’s features within the specified timeframe. Prioritize essential elements to meet the fixed deadline by saying ‘no’ to nice-to-have but unnecessary features. Clear communication with stakeholders ensures that expectations align with the revised scope, fostering understanding and flexibility.

Variable Time, Variable Scope

In projects with both variable time and variable scope, defining either the time limit or the scope early on is essential to recognize project success. Understanding project expectations allows your team to avoid being arbitrarily labeled as a failure. Regularly reassess and redefine the time and scope based on evolving requirements, maintaining an agile approach while ensuring clear expectations.

Fixed Time, Fixed Scope

Unfortunately, projects with fixed time and fixed scope are challenging and prone to failure. To navigate these projects successfully, consider under-promising and over-delivering. Alternatively, leverage waterfall planning to define and de-risk the entire project clearly. While waterfall planning may be unpopular, it proves effective when there are few variables.

Use these projects as learning tools for upper management, showcasing the complexities of software development. Encourage a shift away from rigid scope and time constraints, emphasizing that flexibility yields better outcomes and prevents the pitfalls of poorly written code resulting from rushed projects. Breaking the cycle of cutting corners in fixed-time, fixed-scope projects is essential for your team’s and the business’s sustained success.

3. Address Root Cause

In the dynamic field of software engineering management, the ability to adjust variables is crucial, yet sustained success relies on a strategic focus: addressing root causes. Here’s why it’s paramount:

Balancing Adaptability and Image

While adjustments offer quick solutions, frequent reliance on them can tarnish both the manager’s and the team’s image. A high-performing team excels not just in adapting but in minimizing the need for constant adjustments, demonstrating stability and strategic acumen.

Consequences of Misguided Adjustments

Adjusting the wrong variable has repercussions, affecting the manager and the team. Failing to discern fixed and variable aspects can lead to misalignment, eroding trust and morale, and hindering long-term success.

Trust and Morale

Repeated adjustments without addressing root causes create uncertainty, lowering morale and diminishing trust. Focusing on root causes establishes an environment of stability, vital for a cohesive and productive team. This proactive approach not only prevents recurring issues but also fosters a foundation of stability and strategic problem-solving.

In essence, while adjustments are a managerial tool, addressing root causes is the linchpin for sustained success. By understanding fixed and variable elements, managers cultivate a high-performing team that strategically navigates challenges and consistently aligns with broader organizational objectives, fostering trust and maintaining morale over the long term.

4. Normalize Healthy Change

Encountering unexpected challenges is akin to a flat tire on the road—it doesn’t signify poor driving, but rather the unseen obstacles inherent in the terrain. The ability to swiftly change a flat tire becomes a victory worth celebrating—a demonstration of skills and experience in navigating the unexpected.

Normalizing change extends beyond responding to challenges; it involves integrating them into a culture of continuous improvement. Celebrating each adjustment as a learning experience, coupled with a reflective analysis of the root cause, ensures a team that not only navigates roadblocks but transforms them into milestones on the path to success. This approach fosters a culture that embraces and celebrates change as a vital pathway to growth, steering the team away from a fear of failure and ensuring that adjustments go beyond being mere band-aids, contributing to sustained excellence.

However, regular adjustments to a project may signal underlying issues within the planning phases. Recognizing how often it’s healthy to adjust project variables is crucial. In an environment that encourages risk-taking, frequent adjustments might be appropriate. Conversely, in industries intolerant to risk, minimizing adjustments becomes a strategic approach to maintaining stability.

Perfection is not the goal; rather, it’s about avoiding the repetition of mistakes. Experimentation and growth are vital elements for maintaining a healthy and vibrant team process. While the search for the “perfect” process is a common desire, companies are in a constant state of change. Therefore, teams must evolve to remain successful, adapting to the shifting landscape.

Conclusion: How To Always Win

Success is not a rigid destination, but a dynamic journey shaped by a manager’s ability to define its terms. By skillfully identifying variables, embracing change, and addressing root causes, a manager transforms challenges into opportunities for growth. Normalizing healthy change becomes the bedrock of a culture that not only navigates obstacles but celebrates them as milestones on the path to enduring success. As a manager, you wield the power to define your team’s win by aligning with the business’s evolving priorities and ensuring that, regardless of the road’s challenges, your team always emerges victorious in what truly matters instead of bogged down by unimportant failures.

Best practices for promoting managers from within (and why you should)

Fri, 22 Sep 2023 00:00:00 GMT

The importance of nurturing talent from within cannot be overstated. Promoting employees to new roles, especially within the engineering domain, fosters loyalty and trust and strengthens the company's internal culture.

Internal promotions don’t have to be a struggle. They can be a win-win for both the company and the employees. In this article, we'll delve into seven best practices for hiring engineering managers internally and how to ensure the process is both effective and enriching.

1. Clearly Define Your Hiring Goals

Before you embark on the journey of promoting from within, it's essential to establish clear objectives for the process. Internal promotions should not be a mere formality but a strategic move to retain and nurture your existing talent pool. By providing a path for growth, you demonstrate to your employees that the company values their contributions and is committed to their professional development.

However, it's crucial to emphasize that opening internal applications should not be done merely as a courtesy. It's important to believe fully in the capabilities of internal candidates and their readiness for the role. Doing so without genuine intent to hire them can lead to negative consequences, including a loss of employee confidence in the promotion process and potential talent attrition.

While internal promotions are a valuable strategy, it's also acceptable to consider external hires when they align with your company's deliberate goals. For instance, you may be seeking external expertise to complement your internal talent pool, guide internal promotions, or fill a specific skill gap.

Case Study: InfinitiMind

InfinitiMind, a rapidly growing AI company, faced a critical need for an Engineering Manager. Instead of immediately turning to external candidates, the forward-thinking leadership team decided to prioritize internal talent. They did so by clearly defining their hiring goals and recognizing the untapped potential within their existing team.

Through a structured approach, they identified Rachel, a high-potential engineer, and initiated a mentorship program designed to prepare her for the managerial role. Rachel's successful transition exemplified the company's commitment to employee development and demonstrated its agility in promoting from within, all while saving on recruitment costs.

This strategic decision not only retained employee loyalty but also proved cost-efficient, showcasing the value of nurturing internal talent for leadership growth in a rapidly expanding organization. The benefits were multifold, including streamlined recruitment processes, heightened employee morale, and the cultivation of a stronger internal culture that prioritized growth and development.

2. Prepare Internal Candidates with Interview Insights

The transition from an individual contributor to a managerial role can be daunting. To help your internal candidates succeed, provide them with guidance on what the interview process will entail. While you don't need to disclose exact questions, offering insight into the themes and concepts that will be explored can alleviate anxiety and allow candidates to prepare more effectively.

Remember, your goal is to see the authentic potential of the candidate, not to catch them off guard. Consider organizing mock interviews where their existing manager or a seasoned leader plays the role of an interviewer, helping candidates refine their responses and build confidence.

This practical exercise is invaluable for candidates, allowing them to become familiar with interview scenarios and receive constructive feedback. Additionally, encourage candidates to reflect on their management philosophy and provide written responses to the anticipated interview themes. This self-assessment process not only enhances their ability to articulate their leadership approach but also aids in refining their skills and identifying areas for improvement.

Ultimately, these individualized preparations empower candidates to showcase their authentic potential during the interview process, reducing anxiety, and ensuring a smoother transition into managerial roles.

Case Study: CloudWave Technologies

Facing a need for engineering managers, CloudWave Technologies opted to promote from within. The HR Manager provided all potential internal candidates, including John, a senior engineer, with a list of key interview themes like conflict resolution, project management, and team collaboration. John, recognizing the opportunity, prepared specific examples from his experience to align with these themes. This proactive approach empowered John to confidently showcase their leadership potential during interviews, resulting in a structured and objective promotion process.

3. Leverage Your Inside Perspective

One of the unique advantages of internal hiring is your inside perspective. You have the opportunity to go beyond the interview and gather insights from colleagues who have worked closely with the candidate. Don't rely solely on what is visible; actively seek feedback on how the candidate collaborates, mentors, and handles challenging situations. By taking advantage of this internal knowledge, you can make a more informed decision and demonstrate your commitment to the candidate's success.

However, it's crucial to acknowledge that many sensitive conversations and leadership demonstrations occur behind closed doors, away from public channels. Relying solely on what is seen during interviews and from an outside perspective can be misleading. This approach may unintentionally overlook candidates who demonstrate high levels of maturity and leadership in private settings, leaving them feeling unseen and frustrated when denied opportunities they have been working towards but remain hidden from public view.

Case Study: DataPulse

In the process of evaluating Rachel, a senior engineer, for promotion to the role of Engineering Manager, DataPulse recognized the unique advantages of internal hiring.

By conducting confidential interviews with Rachel's colleagues who had worked closely with her, the company delved deeper than the surface. These conversations unveiled Rachel's adeptness in handling challenging discussions with her product manager, Tom. While these interactions occurred behind closed doors, they demonstrated Rachel's effective advocacy for the engineering team and her ability to bridge departmental gaps.

Tom's feedback highlighted Rachel's hidden leadership potential, underscoring the importance of internal promotions in uncovering talents that might remain concealed from public view.

4. Incorporate Internal Hiring into Employee Growth Plans

To ensure that growth opportunities are accessible and appealing to all employees, it's vital to establish a clear path toward promotions with actionable steps. Opaque or seemingly arbitrary processes can be discouraging and hinder personal and professional development. The objective is to make securing a promotion within your company a straightforward and rewarding journey, surpassing the appeal of job-switching. By normalizing clear career trajectories, you not only retain valuable talent but also foster a culture where employees are motivated to invest in their growth within the organization, ultimately benefiting both the individual and the company as a whole.

To keep your internal candidates competitive, offer avenues for them to acquire the necessary skills and experience. For instance, if managing direct reports is a requirement for the new role, consider offering opportunities for candidates to gain similar experience, such as mentoring interns or leading projects. By doing so, you not only prepare them for success but also demonstrate your commitment to their growth.

Internal promotions should be a part of your organization's growth process, but it's essential to understand that growth doesn't always mean moving into a managerial role. Not everyone aspires to be a manager, and being a skilled individual contributor doesn't guarantee success as a manager. Instead, focus on creating a culture of continuous improvement that respects diverse career aspirations, emphasizing personal and professional development tailored to individual preferences.

Case Study: TechSolutions

TechSolutions, a leading software development firm, redefined talent development by launching a comprehensive career development program that included leadership workshops for engineers.

These workshops equipped employees with essential skills in team management, conflict resolution, and communication, offering a growth path even for those not immediately eligible for managerial roles. The result was remarkable—heightened employee retention and seamless transitions into managerial positions. For example, an aspiring engineer named Michael was given the chance to lead a cross-functional project team, allowing him to develop leadership skills proactively. This approach underscored the vital role of employee growth in achieving long-term organizational success.

5. Use a Different Interview Process for Internal Hires

It can be tempting to use the same interview process for both internal and external candidates in the name of fairness. However, this approach can inadvertently skew the hiring process in favor of external candidates who may have had more opportunities to demonstrate their suitability in different settings.

Recognize that internal candidates, especially those transitioning from individual contributor roles to managerial positions within the same organization, will have fewer direct experiences to draw upon during interviews compared to external candidates. To address this imbalance, it's essential to adjust your interview approach accordingly for internal candidates while still maintaining fairness and objectivity in the evaluation process.

One effective approach is presenting internal candidates with specific hypothetical scenarios relevant to the managerial role they aspire to, allowing you to assess their critical thinking, adaptability, and application of knowledge in real-world situations. This approach emphasizes their problem-solving abilities, communication skills, and decision-making prowess, moving beyond a focus on past performance. This shift towards a tailored approach lowers barriers for internal candidates, fostering inclusivity and a growth-oriented hiring process. It opens opportunities to unearth hidden talents and potential not immediately apparent from their current roles, empowering candidates to excel in new responsibilities, and benefiting both the individual and the organization.

Case Study: InnovateX Labs

InnovateX Labs, a rapidly expanding technology company, encountered a common conundrum—identifying internal talent suitable for managerial roles, despite their limited direct experience.

To address this challenge, the leadership team implemented a customized interview approach with a focus on assessing potential over past performance. One standout candidate, Alex, a proficient software engineer aspiring to a leadership role, demonstrated their abilities through hypothetical scenarios that mimicked managerial challenges. Alex's responses highlighted adaptability, problem-solving skills, and innate leadership qualities, transcending their lack of direct managerial experience.

InnovateX Labs' decision to promote Alex to the role of Software Engineering Manager illustrated the success of assessing internal candidates based on their potential. This approach continued to unveil hidden talents and cultivate a growth-oriented culture within the organization.

6. Assess Readiness Honestly

While internal promotions are undoubtedly a valuable approach to nurturing talent within your organization, it's equally important to maintain a balance between encouraging upward mobility and ensuring that candidates are genuinely ready for the roles they aspire to. The temptation to allow anyone to apply for higher positions in the hopes of a pleasant surprise should be approached cautiously.

While occasional success stories may emerge, this strategy can more often discourage employees from making future attempts when they are truly prepared. Passion and dedication are invaluable assets that shouldn't be underestimated, and it may only take one rejection for an employee to question their future within the company.

As such, open and honest conversations with potential candidates and their current managers become essential in accurately assessing readiness for new roles, helping to prevent disappointment and maintain employees' confidence in their career trajectories.

Case Study: TechGenius Solutions

TechGenius Solutions exemplified its commitment to nurturing internal talent through the case of David, a dedicated engineer aspiring to a managerial role. During a one-on-one conversation with his current manager, Mark, David expressed his career goals.

Rather than immediately endorsing his aspirations, Mark engaged in an open and candid dialogue, focusing on assessing David's readiness for the transition. This honest assessment recognized David's dedication and technical expertise while highlighting the need for further training and development to excel as an engineering manager.

By providing David with constructive feedback and a clear development plan, the company ensured he was well-prepared for his eventual internal promotion.

7. Prioritize Internal Candidates

If you are committed to hiring internally, prioritize your internal candidates in the hiring process. Conduct internal interviews before considering external candidates. This approach demonstrates your confidence in your team and avoids creating a situation where internal candidates feel like backups.

It's essential to align your hiring strategy with your company's specific needs, whether you seek fresh perspectives or value the potential for growth. Prioritizing internal candidates in the hiring process offers several advantages beyond demonstrating confidence in your team.

By conducting internal interviews before considering external candidates, you create a fairer competition. Internal candidates may be at a disadvantage if competing directly with external applicants who may have more extensive interview experience or better preparation for the role. This approach aligns your hiring strategy with your company's specific needs, whether you seek fresh perspectives or value the potential for growth, while also ensuring a more equitable assessment process for all candidates.

Case Study: Nexus Dynamics Group

In the role of HR director at Nexus Dynamics Group, John spearheaded the hiring process for the Engineering Manager position, prioritizing internal talent assessment before considering external candidates. This strategic choice bore several specific benefits for the organization. Showcasing trust in the internal team's potential fostered a sense of belonging and commitment among existing employees, reinforcing their dedication to the company's success.

Moreover, this approach optimized resources by minimizing the need for extensive external candidate searches, saving both time and recruitment expenses. Furthermore, it motivated internal candidates like Lisa, a senior engineer, to perform at their best during interviews, knowing they had the organization's full support. This case illustrates how prioritizing internal hires can boost morale, streamline the hiring process, and empower employees to strive for career advancement within the organization, ultimately benefiting both individuals and the company as a whole.

Conclusion

The implementation of these best practices for promoting managers from within offers significant benefits to organizations. By clearly defining hiring goals, preparing internal candidates for interviews, leveraging internal knowledge, and tailoring hiring processes, companies can unlock the full potential of their existing talent pool.

Additionally, assessing readiness honestly and prioritizing internal candidates not only strengthens the internal culture but also streamlines the hiring process and reduces recruitment costs.

Embracing these practices fosters a sense of belonging and commitment among employees while optimizing resources. Ultimately, these strategies create a supportive environment that fosters growth, builds trust, and leads to a stronger and more vibrant company culture.

It's about realizing the immense potential within your organization and reaping the rewards of internal promotions, benefiting both the company and its employees.