Let’s imagine you are a product manager who recently paired with a new engineering team. You come across a project initiated by a technical lead that you would rather shutdown than watch continue. What would you do in such a scenario? Even if you feel that shutting down the project is best for the company, there is a right way to go about the process.
Are You Sure the Project Needs to Go?
Before you decide you need to put the brakes on an ongoing engineering project, make sure you are on the right track. Some tell-tale signs of a project being in trouble include:
- The team has no detailed project plan.
- There is no clear hierarchy in the team.
- No one from the company’s senior management is backing the project.
- There has been no customer involvement in product definition.
- The customer has not provided any feedback on deliverables.
- There is no use of suitable project tracking tools.
- The team is overworked.
- Team members have ideas about how to provide simpler solutions.
- There has been little to no testing.
- There is no clarity on exactly what’s expected from the final product.
Shutting Down a Project
Every once in a while, there comes a time when a product manager needs to shut down a project started by a technical lead (TL). If you are worried this might reflect poorly on your own performance, don’t be. Here are measures you may follow to make the process go as smoothly as possible.
- Include the TL in your talks with other stakeholders, which include feedback calls. This gives you an opportunity to get a first-hand perspective. For all you know, the TL might also feel that the project needs to go.
- Determine how aligned the project is to your company’s goals, because shutting it down might be easy if it is down the priority list.
- If you can get the project into a beta or minimum viable version (MVY) state with little effort, you may track its adoption (or lack of).
- Begin user-involvement at an early stage, simulate possible results, get required feedback, and make your decision accordingly.
- Speak with stakeholders who wanted the project implemented and find out their reasons. Share with them why you feel moving forward might not be a good idea.
The Alternatives
While you might want to take a firm decision of shutting down a project, think hard in case other stakeholders do not provide their complete support. If you have been tasked with recovering an engineering project, start by looking for signs of over- engineering. In some cases, you might be able to pivot projects by adding capabilities that provide value to end-users. Pay close attention to numbers when justifying a product’s level of automation, be it the number of users or the time saved.
Conclusion
When caught in a dilemma about whether or not to shutdown a project that a technical lead holds close to the heart, determine what’s best for your company. Thinking about sunken costs will do no good, because there’s a good chance you will need to rebuild anyways. Cutting your losses short - and even starting over if you have to - might be in your best interest.