A portfolio intake process decides which ideas earn funding, analysis, and team capacity. Without one, every request arrives through a different channel, and the loudest voice usually wins. As a result, portfolios fill up with half-started work, and leaders lose sight of what is actually moving.
This guide shows how to design a portfolio intake process that controls work in progress. Specifically, it uses the SAFe portfolio Kanban as the model and Jira Align as the system of record. Even so, the same ideas apply if you run intake in Jira Product Discovery or a Jira Service Management request form.
Why a portfolio intake process matters
Most portfolio problems start at the front door. For example, when there is no clear path for new requests, several things go wrong at once:
- Unclear submission paths. People do not know how to propose work, so they go around the process instead.
- Inconsistent proposals. Each request uses a different template, so leaders cannot compare them fairly.
- Overloaded work in progress. Too many initiatives start at once. As a result, none of them finish on time.
- Weak alignment. Approved work does not trace back to strategic themes or forward to epics and features. Therefore, reporting breaks down.
In contrast, a defined portfolio intake process gives every idea the same path, the same questions, and the same decision points. Consequently, leaders can say no, or not yet, with evidence instead of opinion.
How the portfolio Kanban structures intake
SAFe describes the portfolio Kanban as the system that moves epics from idea to outcome. In this model, the Epic Owner coordinates each epic as it moves through the board. Meanwhile, Lean Portfolio Management decides which epics advance, because later steps consume more effort and capacity.
For instance, a common version of the board uses the following states:
| State | What happens | Typical WIP limit |
|---|---|---|
| Funnel | Ideas are captured with a short description. Nothing is turned away at this stage. | None |
| Reviewing | An Epic Owner is assigned, an epic hypothesis statement is drafted, and the epic is ranked with WSJF. | Moderate |
| Analyzing | The Epic Owner builds a lean business case and defines the minimum viable product (MVP). | Tight |
| Backlog | Lean Portfolio Management has approved the epic. It waits for capacity on an Agile Release Train. | Moderate |
| Implementing | Trains pull features into PI Planning, build the MVP, and then pivot, stop, or persevere. | Set by capacity |
| Done | Business outcomes are met, or the epic is stopped because the hypothesis was not proven. | None |
The key design choice in any portfolio intake process is the WIP limit on Analyzing. Business cases take real effort, so the portfolio should only analyze what it can realistically fund. Similarly, the Backlog should stay short, since epics that wait too long often lose their business value.
Setting up portfolio intake in Jira Align
Jira Align supports this flow with a few configurable features. First, decide which one will act as your front door, because every request should enter the same way.
- Ideation. Idea groups collect proposals from internal teams or external stakeholders. Contributors submit ideas, others can vote, and approved ideas can become epics or features.
- Epic intake forms. Custom fields on the epic capture the business case details your portfolio needs, such as justification, requestor, and approver. These fields are also available through the Jira Align REST API.
- Process flows. Configure epic states to mirror your portfolio Kanban, so the board and the reports show the same picture.
- Scorecards and WSJF. Use a consistent scoring method so every epic is ranked on the same scale.
Next, build the intake form for your portfolio intake process. Keep it short at the Funnel stage. A title, a problem statement, the strategic theme it supports, and the sponsor are usually enough. After that, add the lean business case fields only when the epic enters Analyzing.
Finally, link each epic to a strategic theme and a primary program. As a result, the hierarchy runs cleanly from strategy to theme, portfolio epic, feature, and story. For more on that connection, see our guide to the Atlassian Strategy Collection.
A 30-day plan to launch the process
- Week 1: Agree on the rules. Define what counts as a portfolio epic, who can submit, and who approves. Write down the WIP limits for Analyzing and Backlog.
- Week 2: Configure Jira Align. Set up the intake form, the epic process flow, and the scoring method. Then test the flow with two or three real proposals.
- Week 3: Run a portfolio sync. Review everything in the Funnel and Reviewing states. Close or park anything that no longer fits a strategic theme.
- Week 4: Publish and train. Announce the single front door, retire side channels, and train Epic Owners on the hypothesis statement and lean business case.
After launch, review the board at every portfolio sync. In addition, revisit the WIP limits each quarter, especially before PI Planning. For more detail, our PI Planning readiness checklist covers that handoff.
How to measure the portfolio intake process
In addition, track a few simple measures so the process earns trust over time:
- Intake cycle time: days from Funnel to an approval decision.
- WIP compliance: how often Analyzing stays within its limit.
- Approval rate: the share of reviewed epics that reach the Backlog.
- Outcome rate: the share of implemented epics that meet their hypothesis.
Of course, a low approval rate is not a failure. In fact, it often means the process is doing its job by stopping weak ideas early.
Frequently asked questions
Do we need Jira Align for a portfolio intake process?
No. In practice, the process matters more than the tool. However, Jira Align connects intake to PI Planning, roadmaps, and portfolio reporting, which is hard to reproduce in spreadsheets at enterprise scale.
Who should approve epics?
Lean Portfolio Management should make the go or no-go decision. Typically, that group includes business owners, enterprise architects, and portfolio leaders. As a result, they can weigh capacity and budget together.
How detailed should a lean business case be?
Keep it short. After all, the goal is enough information to make a decision and define an MVP, not a full project charter. Therefore, if analysis takes months, the WIP limit is probably too loose.
How VTPMO can help
VTPMO is a team of Atlassian platform specialists with Atlassian Certified Professionals and deep experience in SAFe and Lean Portfolio Management. We have supported Jira Align and SAFe programs for organizations such as Visa and the Federal Reserve Banks. Learn more about our Scaled Agile and Jira Align services and Atlassian services, or contact us to design your portfolio intake process.