Proof of work

Show, don’t tell.

These are the artifacts I build and run on real programs, rebuilt as sanitized samples. The structures are mine; project names and details are illustrative, and the adoption figures are the public OPNAV-GPT numbers.

Portfolio board Adoption dashboard Prioritization RAID log RACI Risk heat map JQL dashboards Status pack How this site runs

Portfolio management

Portfolio health board

Projects roll up to programs and programs to the portfolio. Leadership reads one line per initiative: health, phase, the next decision needed, and open dependencies.

Illustrative sample

Initiative	Program	Phase	Health	Next decision	Deps
Secure AI assistant rollout	Enterprise AI	Light the path	On track	Approve SIPR onboarding wave 3	4
Repository migration to SharePoint Online	Platform modernization	Draw the lines	Watch	Confirm retention labels with records officer	6
Service desk modernization (JSM)	Service operations	Hold the orbit	On track	Accept SLA dashboard	2
Knowledge base restructure	Knowledge management	Map the sky	At risk	Name a content owner per space	3
Event platform requirements	Program operations	Draw the lines	On track	Sign off on the requirements baseline	1

Adoption metrics

Adoption dashboard: OPNAV-GPT

Adoption tracked like delivery: by network, by wave, and by what users can reach. Public figures, rounded down.

Public figures

Pilot

250+

NIPR users

3,500+

SIPR users

3,700+

Total users

7,200+

3,900+knowledge assets available to OPNAV-GPT users

55+enterprise data sources supporting secure AI use

50+reusable prompts in the OPNAV-GPT library

10+cross-functional workstreams coordinated as delivery lead

Prioritization

WSJF scoring

Weighted Shortest Job First: cost of delay (business value + time criticality + risk reduction) divided by job size. The highest score goes first, and the math ends most priority debates.

Illustrative sample

Feature	Business value	Time criticality	Risk reduction	Cost of delay	Job size	WSJF
Single sign-on for secure-network users	13	13	8	34	5	6.8
Prompt library, version 2	8	5	3	16	3	5.3
Records retention labels	5	8	13	26	8	3.3
Usage analytics dashboard	8	3	5	16	5	3.2

Governance

RAID log

Risks, assumptions, issues, and dependencies, each with an owner, a response, and a status reviewed weekly.

Illustrative sample

ID	Type	Description	Owner	Response	Status
R-01	Risk	Account provisioning on the secure network takes longer than the onboarding window	Platform lead	Pre-stage accounts one wave ahead; track in Jira	At risk
A-02	Assumption	Content owners will review migrated libraries within two weeks	Delivery lead	Confirm in writing at kickoff; escalate at day 10	Watch
I-03	Issue	Training sessions conflict with a command exercise	Adoption lead	Record sessions; add office hours the following week	On track
D-04	Dependency	Security accreditation update before the next release	Cyber team	Weekly sync; release gate in Jira	Watch

Ownership

RACI matrix

One accountable owner per activity. Most stalled decisions trace back to two.

Activity	Sponsor	Delivery lead	Platform team	Data owners	Adoption lead
Prioritize the backlog	A	R	C	C	C
Configure workflows and permissions	I	A	R	C	I
Approve data sources	I	C	C	A/R	I
Training and communications	I	A	C	I	R
Release go / no-go	A	R	C	C	C

R responsible · A accountable · C consulted · I informed

Risk

Risk heat map

Likelihood × impact. Anything in the top-right gets an owner and a dated response this week.

Likelihood 15

Vertical axis: impact 1 to 5. R1 provisioning delays · R2 accreditation timing · R3 content owner availability · R4 training conflicts.

Jira

JQL behind leadership dashboards

Leadership reporting should come straight from the board, not a separate spreadsheet. These filters power the gadgets I build for sponsors and program leads.

Working JQL

Overdue work leadership should see

project in (DLV, PLAT) AND statusCategory != Done
  AND duedate < now() ORDER BY priority DESC, duedate ASC

Blocked items and who they wait on

project = DLV AND (status = Blocked OR "Flagged" is not EMPTY)
  ORDER BY updated ASC

Adoption stories in the current increment

project = DLV AND labels = adoption
  AND sprint in openSprints() ORDER BY rank

Aging service requests past SLA

project = HELP AND "Time to resolution" = breached()
  AND resolution = Unresolved ORDER BY created ASC

Executive reporting

One-page status pack

Decisions first, then risks, then progress. A sponsor should know what is needed from them in the first ten seconds.

Illustrative sample

Decisions needed this week

Approve onboarding wave 3 for secure-network users (sponsor)
Name a content owner for each knowledge space (division leads)

Top risks

Account provisioning lead time exceeds the onboarding window. Response: pre-stage one wave ahead.

Progress

Wave 2 complete. Training attendance at target. Prompt library expanded; usage analytics dashboard in build.

Next two weeks

Wave 3 onboarding, retention label sign-off, and the 30-day adoption check for wave 2.

Live proof of concept

How this site runs

This website is wired into the same stack I run for programs. Every inquiry becomes a Jira ticket and a SharePoint record, and Field Notes are written and reviewed in Confluence before they publish here.

Working system

1 · Intake

Website forms

Questionnaire, downloads, and Field Notes submissions post to a secure serverless function on Cloudflare.

2 · Triage

Jira Service Management

Each submission opens a ticket in a dedicated queue, labeled by type, with SLAs and automation for follow-up.

3 · Record

SharePoint Online

Power Automate writes the same submission to a SharePoint list: the relationship register and reporting source.

4 · Publish

Confluence

Field Notes and templates are drafted and approved in Confluence, then synced to this site at build time.

The site’s own roadmap is a Jira board, and its runbook lives in Confluence. Same governance, smaller scale.

The method behind these artifacts Get them built for your program

Work with me

Discuss a role or engagement

A short questionnaire helps me prepare for our first conversation. It takes about three minutes.

Start the questionnaire

Stay in touch through Field Notes

Monthly lessons from real federal delivery work, plus new templates and prompts as they’re released.