TPMO & COE OPERATING SHELL
A cleaner working shell for intake, chartering, RAID, reporting, portfolio visibility, and loosely coupled external system adapters.
Use the assistant for quick navigation and procedural help. Keep the next action obvious.
Manage the active standup, switch saved work, and reopen prior runs without leaving the workspace.
Context and current-state notes are saved raw.
Capture the standup context, organizational pain points, and current-state governance exactly as gathered.
Shape the TPMO operating model, charter, governance bodies, and decision-rights model before the office launches.
Define the risk, assumption, issue, dependency, and control patterns that keep the standup operational instead of theoretical.
Shape the reporting model, dashboard taxonomy, workflow metadata, and tool configuration that make portfolio health visible.
Keep tickets and information radiators adapter-agnostic. Configure the providers in Settings, then use this tab as the launch point.
Connect a ticketing system in Settings. Example: Jira.
Connect a reporting workspace in Settings. Example: Confluence.
Plan how the TPMO pilots, launches, scales, and measures the portfolio over time.
Define capability-building, CoE knowledge systems, change planning, communications, and adoption signals.
User-level credentials override server config. Leave a field blank to keep the current stored value.
Token visibility lives in Settings so the header stays clean and the working area stays focused.
Keep the shell agnostic. Define the ticket workspace and information radiator workspace here, then the Reporting tab will use these settings.
Connected. Tap a skill or say “Hey SassiE”.