(05) PORTFOLIO SETUP
We shape many projects into one honest view, so leaders stop collecting status by hand.
DURATION
1 to 2 weeks
FORMAT
Remote, with a named lead
PRICE
From $1,500
BEST FOR
Companies with many launches
(01) OVERVIEW
What this
really covers.
Once a company runs more than a few launches, the real question moves from one date to which dates collide.
We group your projects, connect shared people and shared dependencies, and build one view leaders can read in a minute.
Where collisions hide
Most portfolio problems are not inside a project. They sit between projects: the same designer booked twice, a platform change that three launches depend on, a release window everyone assumed was theirs.
We map those links first. Once they are in place, a slip in one project shows up as a risk in every project it touches, before anyone has to raise it.
A view leaders will use
Access is set up so executives see the picture without needing a seat of their own. The view opens on the dates that matter this quarter, and every number links back to the work behind it.
01
Project grouping
Projects grouped by team, product or quarter, your choice.
02
Portfolio view
One screen showing every date and where they collide.
03
Shared calendar
A calendar of freezes, releases and shared people.
04
Executive access
Read-only access for leaders, with no seat needed.
(03) HOW WE WORK
Close to your team,
from day one.
We start with a short list of the launches leadership cares about most, then work outward to the projects they depend on.
A named lead runs the setup with your programme or operations team, who end up owning the view.
At the end we sit with leadership for half an hour and walk the portfolio together, so the first time they open it on their own, it already makes sense.
THE CHALLENGE
Tollgate ran fourteen launches at once across two offices. Each one looked healthy alone, but the same designers and the same platform team sat behind most of them.
Leadership learned about collisions only when two launches asked for the same people in the same week.
THE OUTCOME
One portfolio view now shows every date, the people they share and the dependencies between them. A slip in one project appears as a risk in every project it touches.
Leadership reviews the portfolio in ten minutes on Monday, and two collisions were moved a month before they would have happened.
(05) HOW IT RUNS
Three steps, then you run it.
1
We map projects, owners and shared dependencies.
2
We build the portfolio view and shared calendar.
3
We set up access and review it with leadership.
IN PRACTICE
Shared people and dependencies are mapped before the view is built.
