Dillon Issa

App Release Approval

APA is an internal go-live approval tool that gives every release one tracked request instead of sign-offs scattered across chat and email. When a release owner drafts a change, the request opens at the same time to four independent reviewers, QA and Test, Security, Compliance and Legal, and Release and Change Management. Each reviewer records its own decision on the same shared record, and none waits on the others. Any reviewer can send the request back for changes on its own item without discarding the other decisions, and a release only moves to scheduling once all four have approved the current version. Every state change is written to an audit trail and fires an automatic notification, all the way through to production deployment and release-note publication.

Role
Product Manager
Type
Go-live approval workflow
Status
Complete
  • PRD
  • Charter
  • User Guide
  • Wireframe
  • Skeletal App Demo

Problem

  • Release owners chased approvals across chat threads and email, and sign-offs were hard to find.
  • No single record showed who approved what, or when.
  • Reviewers worked one after another, so one slow step held up the whole release.
  • When one reviewer sent a release back, the other approvals could get lost and had to be redone.
  • Leadership had no clear view of where a release stood before go-live.

Solution

  • Combined the scattered chat and email sign-offs into one tracked release request.
  • Set up parallel review so all four reviewers open the same record at once and none waits on the others.
  • Designed the return-for-changes path so one reviewer's changes do not discard the others' decisions.
  • Partnered with QA, Security, Compliance and Legal, and Release and Change Management to set each reviewer's scope.

Results

  • Centralized every release sign-off on one shared record with a full audit trail.
  • Gave reviewers parallel review, so a slow step no longer holds up the whole release.
  • Eliminated lost approvals when a release is returned for changes.
  • Gave leadership a clear status view of where each release stands.

What you can explore here

The skeletal app below is a navigation-only prototype of APA: a status dashboard, the release-request intake form, a request detail record with the four parallel reviews, the reviewer decision panel, and a notifications list. It is illustrative and non-functional; all data is sample data and nothing submits, routes, deploys, or notifies.

Skeletal App Demo

Illustrative skeletal demo, not a functional app. An internal go-live approval tool (APA). Original, representative example. No real client names, data, or systems. Navigation only; nothing here submits, routes, deploys, saves, or notifies.

Screen 1 · Status dashboard

Dashboard

  • 2 Draft
  • 3 In Review
  • 1 Changes Requested
  • 1 Approved
  • 1 Scheduled
  • 12 Deployed
ID Title Requester Status Updated
REL-1042 Billing service v3 D. Issa In Review 2h ago
REL-1041 Export API update D. Issa Changes Requested 5h ago
REL-1039 Sign-in service A. Reyes Approved 1d ago
REL-1038 Search reindex A. Reyes Scheduled 2d ago

Screen 2 · Intake

New Release Request

Request
Attachment
Sample: rollback-plan.pdf

Display only. This control does not open a file picker or accept uploads.

Release details
Readiness checklist (all required to submit)
  • Does this change affect how customer data is handled?
  • Draft notes

Complete all required checklist items to submit.

Screen 3 · Request detail

REL-1042 · Billing service v3.0

IN REVIEW History
Requester
D. Issa
Version
3.0.0
Environment
Staging → Production
Submitted
(sample date)

Description: Adds usage-based invoicing and prorated plan changes. Attachment: rollback-plan.pdf

Reviews

Role Decision Reviewer
QA / Test Approved S. Okafor
Security In Review R. Vance
Compliance / Legal Changes Requested L. Mehta
Release / Change Management Pending Unassigned

Advance to Scheduled is locked: all four reviews must Approve.

Comments (participants only)

  • L. Mehta (Compliance): Please confirm the retention setting for the new billing data fields before go-live.
  • D. Issa (Requester): Updated: retention set to standard billing policy.

Screen 4 · Reviewer decision

Review: Security Request: REL-1042

Request summary

Title
Billing service v3.0
Version
3.0.0
Environment
Staging → Production
Attachment
rollback-plan.pdf
Review context
Security scan complete (0 critical); dependency review clean
Decision

Requesting changes returns this request to the requester and does not affect the other reviews.

Screen 5 · Notifications

Notifications

  • REL-1042 · Compliance requested changes (sample date)
  • REL-1042 · QA / Test approved (sample date)
  • REL-1039 · All reviews approved, ready to schedule (sample date)
  • REL-1038 · Scheduled for deployment (sample date)
  • REL-1030 · Deployed to production; release notes published (sample date)

Read-only · Audit trail

REL-1042: history

Date Event Actor
(sample date) Created (Draft) D. Issa
(sample date) Submitted for review D. Issa
(sample date) QA / Test: Approved S. Okafor
(sample date) Compliance: Changes Requested L. Mehta
(sample date) Requester revised + re-submitted D. Issa

History entries are read-only and cannot be edited or deleted.