PILOT22Kevin M. Clement

Kevin M. Clement

Governance that connects ideas to delivery

The intake, decision forums and delivery standards I established at GID across more than 200 initiatives.

The governance model

Every request starts with a common intake record. Scoring and project size determine its review path. Approved work enters a standard delivery and oversight process.

  1. Global Technology IntakeCapture the business need and sponsor in a common request record.
  2. PMO triage and scoringAssess impact, vendors, duration, risk and capacity. Size as sand, pebble or rock.
  3. Core Technology reviewWeekly review. Route rocks to the Technology Governance Council.
  4. Technology Governance CouncilMonthly review of rocks, chaired by the CTO with executive and technology leaders.
  5. Approved deliveryProject plan and RAID, with clear ownership, dependencies and delivery standards.
  6. Oversight and closeoutWeekly status, monthly executive highlights, benefits review and lessons learned.

Sand and pebble requests can proceed from Core Technology review to approved delivery. Rocks also receive Council review. Triage target: 3 days. Approval target: 1 week.

Executive accountability

The CTO chairs the Council with the CFO, CAO, Chief Strategy Officer and technology leaders. Decision history, escalation paths and executive updates make priorities and tradeoffs visible.

Reconciled 111 previously missing projects into a common portfolio view.

Standards that support execution

Mandatory project plan and RAID. Standard charter, requirements, design, testing, change and communications artifacts.

Reusable presentations support intake, project status and closeout decisions. Smartsheet blueprints, SharePoint Project Hub, training and office hours support adoption.

Discuss your next transformation.

Connect with me about Finance technology, AI delivery and enterprise governance.

Email Kevin