Six projects. Competing priorities. Finite resources.
Before deciding what to delay, I wanted to explore a different question: Can we find a way to deliver everything?
Explore The Tradeoff →The Tradeoff is an interactive simulation of creative delivery decisions. Visitors can adjust business priorities, explore resource allocations, and preview the consequences for staffing, schedules, and budgets before committing to a plan.
Make the consequences visible. Keep the decisions human.
When every commitment is a priority, I start with the business goals behind it: what each stakeholder is trying to achieve, where those goals converge, and where they genuinely compete. Establishing that shared outcome gives us a basis for resolving disagreement and deciding how to move forward.
My first instinct is to find a way to deliver every commitment. I examine sequencing, capacity, outside support, and scope before recommending a compromise. Each option has to make sense across the whole operation: solving one delivery problem can create another elsewhere.
Customer trust and quality carry particular weight in my decisions. Strategic opportunity and revenue matter alongside them, evaluated against the outcome and the investment required to achieve it. A decision can be justified by the capability or future opportunity it creates, provided those assumptions and costs are explicit.
Identify the goal behind each request and who owns it. Find the common outcome before treating competing requests as competing interests. Where priorities remain in conflict, make the decision and its ownership explicit.
Examine what a deadline represents, the quality bar, and the consequences of changing either. Customer trust depends on both delivery and clear communication when expectations need to change.
Account for skills, context, onboarding, review, and the work displaced by a reassignment. A team may stretch for an important commitment, but belief in the work does not remove the cost. The reason, duration, and consequences of that stretch need to be understood.
Trace the approvals, inputs, and people the work depends on. Establish who can resolve each blocker and who has authority to approve a change. Additional production capacity cannot clear an independent approval gate.
Weigh immediate revenue against the broader outcome, including strategic opportunity and future capability. Examine the full delivery cost, the assumptions behind the expected value, and the opportunity forgone by choosing one path over another.
Bring stakeholders a recommendation, the tradeoffs behind it, and the expected outcomes of the alternatives. Secure agreement or escalate according to the decision's ownership. Revisit the plan when new information changes its assumptions.
Early in Massive Black's history, we accepted an engagement that expanded our services. It was a strategic opportunity we wanted to pursue, but our existing team and processes were not fully equipped for the work. We would need external specialists at higher rates.
As Executive Producer, I assessed feasibility and the tradeoffs, recommended a path, assembled and hired the team, and planned the budget and schedule. We chose to absorb the additional staffing cost as an investment in a service area we wanted to develop.
Some production processes were being established as delivery progressed. During execution, a delay emerged. We informed the client when it became apparent; late delivery had not been part of the plan. The work was delivered to an exceptional standard, but it was late.
The quality helped preserve the client relationship and earn further work. We built the team to continue that new revenue stream and became more selective about accepting similar engagements once we understood their demands. The experience made the cost of organizational readiness tangible.
The staffing investment was deliberate. The delay emerged during execution. Recognizing that distinction matters: leadership includes choosing which risks to accept, communicating when assumptions fail, and carrying the learning into the next commitment.
Change the relative importance of pipeline, visibility, and adoption. Inspect each project's staffing, budget, deadline, and dependencies. Compare internal staffing transfers, approved budget transfers, outside support, and scope changes.
Preview the impact across the affected projects, then record or discard the proposed plan. The decision history keeps the choices visible. Approval gates remain separate: additional staffing cannot resolve customer or legal clearance.
These decisions often happen across separate schedules, budget sheets, and conversations. A proposal can look sensible in one project while quietly creating a problem in another. Seeing the affected work together makes that consequence easier to discuss before anyone commits.
The useful view connects strategic intent to individual assignments, budgets, and approvals. A staffing change can affect another deadline; a budget transfer can reduce another team's options. Seeing those dependencies together helps leaders assess the full consequence of a recommendation.
The Tradeoff gives people a shared scenario to react to: move these hours, transfer this budget, request this support, or change this scope. Preview the consequences, challenge the assumptions, and record the proposed plan. The value is a clearer conversation and a more accountable decision; the simulation itself does not prove a forecast or supply a universal right answer.
The principle: Make the consequences visible. Keep the decisions human.
An independent experiment using fictional projects and illustrative staffing, budget, and delivery assumptions. It models possible consequences; it does not book people, approve spending, or make decisions for stakeholders.