Project vs Product management

Project vs Product management

The blog entry presents the following case:

🔣 An e-commerce SMB needs to prepare for Black Friday and Cyber Monday, and had 4 months left.
🔣 Problem: they were implementing a new email marketing platform, and in the past week alone, 3 team members said they'd never deliver on time.

After a closer review it turned out that:

➖ Team members didn't understand what they were building: they disagreed over benefits, features, and priorities while a project manager was trying to make an impossible deadline. This caused confusion and arguments.
➖ There wasn't any split between product (iteration) and project (one-time execution) approaches. All in a context were the company was replacing a legacy system (project) while also introducing new functionalities (product).

Solution:

✅ A product owner was appointed, and he defined the goals – or in other words, the result of the work that was needed to be done. This one responsible defined:
🔣 Position, vision & strategy
🔣 Then defined a roadmap, set priorities
🔣 Then translate the roadmap into a plan
🔣 And turn requirements into a scope

As result:

The platform went live just in time, and the repurchase rate went up by 6% within 3 months⚡

Conclusions:

❗ Separate product development and integration projects:
➕ The product manager define the why & what. They are responsible for the vision, strategy, positioning, and building of a product roadmap.
➕ The project manager is concerned with when & how. They manage stakeholders and risks, run a team, and safeguard project boundaries.
❗ Ensure every product, process & system has one owner.
❗ Start every project with clear benefits & outcomes: your team needs to know what is doing and have a clear purpose.

#useful_weekend

From the same blog:

How to work with a bottleneck in your team

⚓️ SurfGate — direct provider: P2P y UPI Collect in 🇮🇳, ACQ in Europe. Our web