Project Portfolio & Sprint Dashboards

When engineering, design, and marketing resources were shared across projects, isolated project schedules could not surface conflicts and delays early enough.

We needed a shared view that connected portfolio priorities with the sprint-level units where work actually happened.

The portfolio dashboard captured status, priority, accountable teams, and the next milestone across concurrent initiatives.

Executives and functional leads could use the same view to identify resource conflicts and schedule risk early.

Each year, the company set two to five main initiatives based on the direction announced by the CEO. I registered those confirmed initiatives in the Asana portfolio, focused up to 80% of business-unit resources on the one or two priorities most critical to the year's success, and set each as a portfolio milestone. I then classified the delivery projects required to achieve those milestones by tier.

• Tier 1 — Executive leadership owns final approval and major situational decisions
• Tier 2 — Executive leadership owns final approval; the Product Business Lead owns major in-flight decisions
• Tier 3 — The Product Business Lead owns final approval and operating decisions

Annual main initiatives

2–5

Top-priority initiatives

1–2

Resources focused on top priorities

Up to 80%

Decision-right levels

3 tiers

Matching decision rights to business impact reduced approval bottlenecks across delivery teams, business-unit leadership, and executive leadership.

The more strategic the initiative, the more teams and resources it required, increasing the risk of unforeseen capacity loss and schedule change. When an uncontrollable incident or resource departure was likely to affect a core milestone or delivery date, I did not wait for a reporting cadence. I surfaced the expected impact and potential schedule change to executive leadership as early as possible.

When an issue could be resolved within the business unit and did not require an immediate executive decision, the accountable team continued the resolution and reported its status and outcome in the weekly business-unit meeting. This kept executive attention on decisions that required intervention while allowing solvable issues to move without delay.

I did not escalate every issue. I designed the operating model so the right decision owner could act at the moment their judgment was needed.

Toss Brand Day and FortuneAid's age-gated adult content category were both targeting mid-September, creating a capacity conflict across the same planner, designer, frontend engineer, and backend engineer. Rather than run both initiatives in parallel, I needed to sequence them around the launch window where each could create the greatest business impact.

Toss could accommodate our schedule, but I placed Brand Day on September 15 to align its reach with the start of the New Year fortune season. Using a planning assumption of 10% CTR across a targetable audience of up to 100,000 and a 48% signup success rate, we projected roughly 10,000 visits and 4,800 new signups.

I focused the four-person cross-functional team on Brand Day for approximately two weeks and moved adult verification and category delivery to mid-October. The content team advanced item selection and content planning in parallel, reducing development wait time while avoiding launch cannibalization with the New Year releases.

As Product Business Lead, I consolidated feasible dates with the engineering and content leads and presented the recommendation in the executive strategy meeting. The FORCETELLER Business Unit CEO approved the resource allocation and launch sequence. I equipped the content lead with the rationale that maximizing launch impact mattered more than launching early; the content team then aligned the revised mid-October date with the CP partner without relationship issues. A one-week post-launch review would feed traffic, signup, and purchase outcomes into the next allocation decision.

Targetable reach

100,000

Planned CTR

10%

Projected signups

4,800

Focused allocation

8 person-weeks

Strong prioritization is not about abandoning one initiative. It is about sequencing both for their best chance to succeed.

The sprint dashboard translated project goals into executable dates while tracking dependencies across engineering, design, marketing, and app review.

When delays or resource conflicts emerged, I escalated them to the accountable owners instead of waiting for the next weekly report.