Control Tower Guide
Understand the program faster.
Control Tower gives leaders and teams a common operating view for complex transformation programs: what matters, what is ready, what is blocked, and where action is needed.
Core Concepts
What each term means
Control TowerThe operating platform for the transformation. It connects strategy, architecture, planning, execution, testing, risk, and run-state signals.
ProjectA transformation environment for one customer, program, or major initiative.
InitiativeAn optional layer for large programs with multiple major value streams under one governance model. Most projects do not need it.
TeamA process area, corporate function, platform area, or delivery track such as sales, finance, procurement, HR, AI, data, integration, security, or change management.
Business CapabilityA stable business or operating capability that requirements can implement, improve, automate, or retire.
Lifecycle StageA transformation step such as Mobilize / Setup, Discover, Select Software, Select SI / Partner, Define, Design, Plan, Build, Validate, Rollout, and Run.
FeatureAn app capability used to manage the work, such as Discovery, Strategy, Architecture, Planning, Implementation Control, Run-State, Setup, Users, and Notifications.
RequirementA capability, business need, build item, or architecture-derived item that must be planned, owned, delivered, and tested.
ReleaseA planned delivery increment with scope, dates, milestones, capacity, requirements, and readiness signals.
MilestoneA date-driven checkpoint with readiness criteria, deliverables, confidence, and management attention indicators.
RAIDRisks, assumptions, issues, and decisions that can affect delivery, quality, cost, or value.
DecisionA leadership choice with owner, options, timing, impact, and status. Important decisions should not be buried in meeting notes.
DependencyA relationship showing that one requirement, team, system, milestone, vendor, or decision depends on another.
AcceleratorReusable best-practice content that helps teams avoid starting from a blank page.
Big RockAn executive-level decision, dependency, or action that can materially affect value, timing, scope, or readiness.
Operating Hierarchy
Simple by default, deeper when needed
WhyGoals and success criteria define the value the program is trying to create.
WhereTeams define the process areas, modules, regions, or functions doing the work.
WhatCapabilities and requirements define the scope that must be delivered or changed.
WhenReleases, milestones, activities, baselines, holidays, and capacity define timing and feasibility.
RiskDependencies, decisions, RAID, blockers, confidence signals, and operating-model gaps explain what could slow delivery.
Roll-upProject Home turns connected work records into executive status, root causes, and actions.
Lifecycle Map
Stages are the journey; features hold the evidence
Mobilize / SetupSetup, users, affiliates, access, workstreams, accelerators, and governance.
DiscoverDiscovery Assistant, strategy inputs, architecture discovery, requirements, and RAID.
Select SoftwareBusiness needs, demo scenarios, architecture fit, platform decision evidence, and RAID.
Select SI / PartnerDelivery approach, named team, assumptions, estimates, governance model, and risk evidence.
DefineGoals, pain points, success criteria, scope, business case, and release intent.
DesignSystems, data, interfaces, system of record, access control, and conversion readiness.
PlanReleases, milestones, deliverables, resources, environments, capacity, SOW, and baselines.
Build / Validate / Rollout / RunRequirements, build flow, testing evidence, go-live readiness, hypercare, support intake, and operating KPIs.
Built-In Accelerators
Start from proven patterns
RequirementsReusable transformation requirements by team and business capability.
KPIsSuggested success criteria for cycle time, quality, adoption, cost, leakage, readiness, and operating performance.
RAIDCommon risks, decisions, assumptions, blockers, and test scenarios that show up in enterprise programs.
Architecture InputsSystems, interfaces, data ownership, conversion readiness, roles, and access-control patterns.
Planning ModelRelease, milestone, activity, resource, environment, holiday, SOW, and baseline structures for agile-hybrid delivery.
Run-State ControlsOperational backlog, release support, enhancement intake, readiness ownership, and continuous improvement signals.
AI Assistance
Turn input into usable signals
Discovery InterpretationConvert notes, documents, transcripts, and fit-gap inputs into candidate goals, pain points, requirements, RAID, systems, and data records.
Guided DiscoveryUse topic-based questions and information requests to make discovery more complete and less dependent on blank-page interviewing.
Confirmed FindingsReview AI-suggested interpretation before it becomes part of the project record.
Signal SurfacingBring blockers, ownership gaps, milestone concerns, readiness gaps, and delivery pressure into the operating view.
Contextual Starting PointsApply accelerators where the work happens instead of searching through separate templates.
Executive VisibilityUse connected data to reduce status-reporting effort and focus leadership attention on the items that can change outcomes.
Status Colors
How to read signals quickly
Ready / On TrackEnough connected data exists and no material blocker is visible.
Open with Gaps / At RiskWork can continue, but something needs attention before leaders can trust the signal.
CriticalBlocked, late, failing, or likely to affect delivery unless acted on.
Baseline NeededThe app needs more setup or data before it can calculate a useful signal.
How To Use It
Simple operating rhythm
Start with Project HomeUse it to see executive signals, lifecycle readiness, team health, needs-attention items, and usage signals.
Open the evidence behind signalsAmber and red cards take you to the data behind the signal, not another status deck.
Keep the record currentStatus reporting becomes easier when requirements, owners, tests, milestones, risks, and decisions live in the same platform.
Guide