This is a chart that I prepared by combining the SE lifecycle model and the Return Map diagram.

The reason I did this is because Systems Engineering focus on costs, schedules and quality aspects of the lifecycle but doesn’t emphasis enough on the time value which helps in the decision-making process. Return Maps on the other hand are very high level and do not provide means to granularly monitor the returns. The Return Factor comes into play only after MR.

Through this chart I try to bring focus on three points

1. How does one track the economic impact at each stage?
2. How do you reduce the time required for each stage?
3. How do you prolong a product’s valuable lifetime?

How do you track economic impact throughout the lifecycle?

I would recommend using the Net Present Value (NPV) metric before MR and Return on Investment (ROI) thereafter. This is because in most cases the exact pricing is not known in the early stages, however there are benefits that can be visualized and accounted.

How do you reduce the time required for each stage?

A few high-level guidelines to reduce TTM

• Ensure each member understand what needs to be accomplished, by when and what their role will be
• Ensure each member understands the complete task loop. When is the task considered “complete”?
• In a distributed team, try to keep an eye on the approach that individual team members are taking to avoid duplicate efforts and different approaches of doing their part. e.g one codes in a monolithic way, while the other follows a modular structure
• Shield the team from distractions to avoid refocusing time. Focused efforts are more productive
• Encourage the team to get to a conclusion sooner on their task

If you’re reading this, please share your thoughts and comments below. And if you plan to use any part of my work feel free to do so by a simple acknowledgement or reference to my work. Thank you for reading!