The Doctrine of Completed Work
Early in my career, I proposed a refactor for our notification service. The goal was to simplify the overly complex and difficult-to-maintain system.
However, my idea didn’t see the light of day. I was too focused on the problem and didn’t present a defined solution or clear path forward.
I didn’t understand why my proposal wasn’t well received until much later in my career...
That’s when I learned about the doctrine of completed staff work.
This principle taught me to develop solutions and map actionable steps before presenting.
Embracing this approach can strengthen our proposals and significantly boost our career progression as software engineers.
What is the Doctrine of Completed Work?
The doctrine of completed work emphasizes the importance of fully completing tasks and projects before moving on to new ones. Originating from project management and productivity methodologies, it underscores the value of delivering comprehensive and well-executed solutions rather than merely identifying problems or partially addressing them.
The doctrine of completed work is made up of 4 critical steps:
- Identify the Problem: Ensure that a clear issue is defined & communicated.
- Define the Solution: Generate well-thought-out, actionable solutions rather than just highlighting issues.
- Outline the Clear Path Forward: Outline a step-by-step plan to achieve the desired outcome.
- Present the Plan: Share your plan with your team or boss to ensure everyone is on the same page.
Benefits of the Doctrine The doctrine of completed work offers several key benefits for career progression as a software engineer:
Builds a Strong Reputation
Delivering complete, well-thought-out solutions consistently helps build a reputation for reliability and competence. Colleagues and supervisors will recognize you as someone who sees projects through to completion, making you a valuable team member.
Improves Problem-Solving Skills
Focusing on the doctrine encourages you to think through problems thoroughly and develop comprehensive solutions. This enhances your problem-solving skills and enables you to tackle more complex challenges effectively.
Demonstrates Reliability and Consistency Adhering to the doctrine demonstrates your ability to manage tasks and projects reliably. This consistency is crucial for career advancement, showing managers you can be trusted with essential responsibilities.
Applying the Doctrine of Completed Work
Using my early career experience with the notification service refactor, here’s how I should have approached the proposal by applying the doctrine of completed work:
- Fully Understand the Problem
Dive into specific issues and their impacts. Gather quick feedback from the team for a broader perspective.
- Develop a Defined Solution
Create a clear refactor strategy with specific changes and tools. Anticipate potential challenges and plan solutions.
- Outline a Clear Path Forward
Break down the refactor into manageable steps with timelines. Ensure each step is actionable and builds on the last.
- Prioritize Quality
Refine the plan to cover edge cases and ensure robustness. Focus on delivering a clear, high-quality proposal.
I could have presented a more compelling and actionable proposal by following these steps.
This approach demonstrates a solid understanding of the problem and a clear path to a solution, making it easier for the team to see the project’s value and feasibility.
The doctrine of completed work is a valuable principle for any software engineer aiming to progress in their career.
By focusing on fully developing solutions, outlining clear paths forward, and ensuring quality and completion, you can present more robust, more compelling proposals.
Reflecting on my early experience with the notification service refactor, I learned that delivering well-rounded and actionable solutions is vital to gaining the support and trust of your team.
Embracing this doctrine can help you build a strong reputation, enhance your problem-solving skills, and demonstrate reliability and consistency.