CTI-CMM version 1.1 is here!
Get your hands on the CTI-CMM and start growing your program now. The most recent version of the CTI-CMM is version 1.1, available for download below.
Your input matters! If you have any feedback for us please use this Google Form.
Before starting the journey using the CTI-CMM, we recommend becoming familiar with the model, its design, and intended purpose(s). This model provides CTI programs with direction to engage potential organizational stakeholder, align with their workflows, and optimize the level of CTI support to them. This all starts with identifying which stakeholder types your program seeks to support and can support, identifying growth blockers, establishing a roadmap, executing against it, then evaluating effectiveness. For ease of implementation, we break these areas out into the respective phases below.
Understanding existing capability provides a key foundation on which we can benchmark and grow from. This phase is dedicated to taking stock in existing stakeholder support and program capabilities via self-evaluation. For each domain, rate your current maturity across a four tier scale: CTI0 representing no capability, CTI1 a partial implementation, CTI2 largely implemented, and CTI3 for a fully implemented capability.
We recommend downloading the CTI-CMM beta assessment tool as a stand-alone spreadsheet designed to assist CTI programs with this phase.
This phase focuses on identifying core areas in which the CTI program should seek to grow, devising a reasonable path forward via a roadmap that includes growth milestone. CTI programs may consider using the 30-60-90-180 day structure to identify growth goals.
In this phase, you execute the envisioned plan through a series of people, process, and technology improvements aligned to grow stakeholder traction. This often requires deploying resources to re-engage existing stakeholders while concurrently pursuing new ones to support to achieve your maturity growth goals.
After an action plan has been established, decisions made, and operations resumed, we suggest introspecting on program growth. Program growth does not happen over night, so we suggest reviewing progress on a bi-annual cadence.