Optimizing the Project Intake Process

We fix the project intake process by replacing static spreadsheets with a tiered scoring rubric that mandates Cost of Delay quantification at the point of entry. This system forces requesters to justify resource allocation against strategic impact before a single hour of engineering time is committed, preventing the "frozen front-end" bottleneck common in organizations running 20+ concurrent initiatives.

When does a spreadsheet-based intake process officially break?

Spreadsheets are the default starting point for most R&D organizations, but they possess a low ceiling for complexity. We observe that manual systems fail once intake volumes exceed 50 new requests per quarter. At this scale, version control chaos and data fragmentation become inevitable. A spreadsheet is a passive repository; it cannot enforce the logic required to differentiate a critical infrastructure upgrade from a stakeholder's pet project.

Manual systems lack forced trade-offs. Without a structured rubric, stakeholders default to labeling every initiative as "High Priority." There is no economic friction to prevent this behavior. Consequently, Program Leads lose roughly 40% of their work week to manual screening and chasing missing context from incomplete submissions.

This administrative load creates the "frozen front-end." Requests sit in a backlog for weeks because the data provided is insufficient for a decision. The R&D lead cannot approve a project without knowing its cross-functional dependencies, yet the spreadsheet does not mandate that information. The result is a stagnant queue that frustrates the business and obscures the true capacity of the R&D engine.

Quantifying the economic impact of waiting

To move beyond gut feelings, we introduce Cost of Delay (CoD) as the primary metric for triage. Static forms capture what a stakeholder wants to build. Our rubric captures what happens if we do not build it now. We calculate CoD by scoring three distinct components: user-business value, time criticality, and risk reduction or opportunity enablement.

This approach utilizes Weighted Shortest Job First (WSJF) logic. By dividing the Cost of Delay by the estimated job duration, we ensure that high-value, short-duration projects move to the front of the capacity planning phase. This prevents large, low-value "anchor" projects from blocking the flow of high-leverage work.

Shifting the conversation to economic impact changes the power dynamics of the intake meeting. When a project is deprioritized, it is not because the R&D lead "said no." It is because the project's quantified economic impact was lower than the alternatives currently in the queue. This objectivity is essential for maintaining alignment between R&D and the broader executive team.

What criteria should define a Tier 1 project request?

Not all requests deserve the same level of scrutiny. We categorize initiatives into tiers to ensure executive oversight is reserved for the highest stakes. A Tier 1 project is defined by specific, non-negotiable thresholds.

Strategic Alignment: The project must demonstrate direct alignment with at least two primary corporate pillars for the current fiscal year.
Resource Intensity: Requirements exceed 15% of total R&D capacity or involve cross-functional dependencies across three or more departments.
Risk Profile: The initiative carries significant market risk, technical debt implications, or regulatory requirements that necessitate a formal steering committee.
Documentation: Tier 1 requests require a full business case, including a multi-year ROI projection and a detailed risk mitigation plan.

By setting these high bars, we filter out noise. Tier 2 and Tier 3 projects can be handled through delegated authority, but Tier 1 projects require the Head of R&D and the COO to personally validate the trade-offs involved.

How do we handle emergency walk-up work?

Unplanned work is a reality that breaks rigid systems. We address this by reserving a fixed percentage of R&D capacity—usually 10-15%—specifically for operational "keep the lights on" (KTLO) and emergency work. This buffer prevents the entire roadmap from collapsing when a critical bug or urgent compliance issue arises.

Emergency requests must still pass an abbreviated triage. We do this to ensure they are not "stealth projects" attempting to bypass the rubric. If an emergency request exceeds the reserved buffer, the requester must identify which active project will be paused. We do not allow "just fit it in" as a management strategy.

We track the frequency and source of walk-up work as a core KPI. If a specific department consistently exceeds its emergency allocation, it indicates a systemic gap in their quarterly planning. We use this data to adjust future capacity and hold departments accountable for their planning accuracy.

Who owns the final decision in the triage meeting?

Accountability for the intake funnel must be singular. While Product Owners provide the "value" score, the Head of R&D or a designated Program Lead owns the final decision. This ensures that technical feasibility and resource availability are the ultimate constraints.

The triage meeting occurs weekly. Rapid feedback loops are the only way to prevent the backlog from stagnating. During these 45-minute sessions, the leads review the top 10% of scored requests. Decisions are recorded in one of three ways:

Approve for Planning: The project moves to detailed scoping and capacity matching.
Backlog for Later: The project is valid but lacks the relative value to displace current work.
Reject: The project does not meet the rubric threshold. We provide the specific rubric-based reason to the requester immediately.

Realities of vetting volume

A mature R&D organization can realistically vet 15-20 high-quality Tier 1 and Tier 2 requests per month without degrading decision quality. If an organization finds itself attempting to vet more than 25 requests, it usually indicates a lack of pre-filtering at the department level.

We use the tiered rubric to automatically reject or redirect requests that score below a minimum threshold. This reduces the manual vetting load on senior leadership. Efficiency is not measured by how many requests we process, but by the ratio of vetted requests that successfully reach the delivery phase. If 90% of approved projects are stalling mid-execution, the triage criteria are too lenient.

The Triage Playbook: From Intake to Roadmap

Replace Open-Text Fields: Remove the generic "Description" box. Replace it with weighted dropdowns for Strategic Alignment, Revenue Impact, and Urgency.
Mandate Cost of Delay: Require a dollar-value estimate for every month the project is postponed. If a requester cannot estimate this, the project is not ready for triage.
Execute the Weekly Sync: Set a recurring 45-minute meeting with R&D, Product, and Finance leads. Only review the top-scoring 10% of the intake queue.
Publish the Intake Dashboard: Give stakeholders a real-time view of where their request sits. Transparency reduces the number of "status update" emails sent to program leads.
Audit the Rubric: Conduct a quarterly review of the scoring weights. As corporate strategy shifts from "growth at all costs" to "efficiency," your rubric weights must shift accordingly.

The Honest Tradeoff

Manual spreadsheets offer superior flexibility for small, highly experimental teams where the cost of a "wrong" project is low. In those environments, the overhead of a formal rubric would outweigh the benefits of governance. Furthermore, structured rubrics can inadvertently penalize radical innovation. Transformative ideas often defy existing strategic pillars or have ROI profiles that are difficult to quantify. By forcing every idea through a rigid economic filter, we risk building a portfolio of safe, incremental bets while missing out on market-shifting opportunities.

In one breath

We scale R&D intake by replacing subjective spreadsheets with a weighted rubric that calculates the economic Cost of Delay for every request. This system forces stakeholders to justify their demands against strategic pillars before they reach the triage meeting. While this adds rigidity that may filter out some highly speculative ideas, it ensures that the R&D engine remains focused on the highest-leverage work.