Phase 1 Path B is optional. If stakeholder alignment already exists and requirements are clear, you can skip directly to Phase 2 — Requirements Refinement & CAB.
Before you start
You will need:- A BlueGenAI account and an active project
- Any existing documentation about the current system — process flows, screenshots, user guides, or requirements documents
- A plain language description of what the modernized system should do
How to generate a stakeholder alignment prototype
1
Create a new project
Open BlueGenAI and click + Create Project. Name it for the modernization effort.
2
Upload existing documentation
Click the Files icon and upload any documentation you have about the current system and the desired future state — requirements documents, process flows, screenshots of the existing system, user guides.
3
Write your first prompt
Describe what the modernized system should do. Focus on the user experience and key capabilities — not technical implementation details.Example:
4
Review and iterate
Review the generated Draft App. Continue prompting to refine until the prototype reflects the agreed-upon vision for the modernized system.
The Draft App generated in the Prototype tab is functional rendered code — not a static image or wireframe. It is one click away from becoming a fully deployed production application by switching to the Build tab. Stakeholders reviewing the prototype are seeing something very close to what the production system will look like.
How to generate a concept of operations document
A concept of operations (ConOps) document describes the current state, the future state vision, key stakeholders, and the high-level implementation approach. It is a standard artifact for leadership review and approval.1
Write a prompt requesting the ConOps
Reference any uploaded documentation so the agent generates content aligned to your specific system.Example:
2
Review and adjust
Review the generated document. Continue prompting to adjust language, add sections, or align to your agency’s document standards.
3
Save the file
Click the save icon on the generated file card. The document is saved to your project’s Files panel and can be downloaded for leadership review.
How to use the prototype for leadership approval
1
Generate a shareable link
Open the 👤 Manage Collaboration panel and toggle Shareable Link Access to On.
2
Share with leadership and stakeholders
Copy the shareable URL and distribute it for asynchronous review. Recipients must be logged in to BlueGenAI to view the link.
3
Walk stakeholders through the prototype
Use the prototype in a presentation or meeting to walk stakeholders through the proposed modernized system. The prototype is interactive — stakeholders can click through it in real time.
4
Collect feedback and iterate
Gather feedback from stakeholders and continue prompting to adjust the prototype until alignment is reached.
5
Disable the share link
Once the review period ends, toggle Shareable Link Access to Off in the Manage Collaboration panel.
When to skip Phase 1 and go directly to Phase 2
Phase 1 Path B is the right starting point when stakeholders need to see something before they can agree. If that alignment already exists, skip it. Go directly to Phase 2 if:- Stakeholders are already aligned on the future state vision
- Requirements exist from a previous effort or discovery phase
- The modernization scope is already documented and approved
Phase 2 — Requirements Refinement & CAB
Proceed here once stakeholders are aligned. Phase 2 transforms your existing system artifacts and approved vision into structured, traceable requirements.
Tips for effective stakeholder alignment
- Show, don’t tell. A working prototype drives faster alignment than a slide deck. Stakeholders can click through the proposed system and react to something concrete.
- Start with one workflow. Prototype the most contentious or highest-priority workflow first — the one most likely to generate disagreement. Resolve that alignment before expanding scope.
- Document decisions as you go. Use the Prototype tab to generate a running requirements or decisions document alongside the prototype. This becomes the input for Phase 2.
- The prototype is production-ready. Remind stakeholders that what they are reviewing is functional code — not a mockup. Their feedback directly shapes the application that gets built.
Related pages
Phase 1 Path A — BD Solutioning
Responding to an RFP or building a proposal? Use Path A instead.
Phase 2 — Requirements Refinement & CAB
Once alignment is reached, move to Phase 2 to develop structured requirements.