A personalised, evidence-based route from where Jordan is today to the CIO destination they've set, and what would have to be true to hit it in five years.
Your CIO destination is plausible, but the five-year target requires faster movement into enterprise strategy and governance. Another qualification is unlikely to materially improve your pathway.
Secure ownership of an enterprise-wide initiative within the next 6 to 12 months. It's the single lever every other recommendation sits behind.
Taking another delivery-heavy role that increases scale and salary without increasing enterprise authority, budget, or governance exposure.
Your strongest evidence is delivery leadership. The missing signal for an executive pathway is broader enterprise strategy ownership.
Six-month goal: 2 CIO/CTO-level executives, 1 executive recruiter, 1 industry peer, 1 governance-level contact.
Pursue a steering committee, governance board, advisory group, or investment committee seat.
Strong transformation history · credible enterprise experience · programme leadership · sufficient credentials · healthy market position.
Limited enterprise strategy ownership · insufficient P&L or budget accountability · weak governance exposure · limited executive/recruiter network · low external visibility.
Weights are calibrated to the CIO/executive-track destination: Leadership and Network carry more weight here than they would for a Principal Specialist track.
Leadership: why 64, not higher. Strong programme-leadership evidence, but limited evidence of permanent organisational leadership, budget ownership above AUD 5M, or P&L accountability, all expected at Director level and above.
Benchmark cohort: 15 professionals who reached CIO or equivalent enterprise technology-executive roles in comparable Australian organisations over the last decade, drawn from official leadership pages, public filings, and professional association listings.
| Signal | You today | Benchmark |
|---|---|---|
| Total experience | 12 years | 14 to 19 years |
| Director/equivalent role | No | Common |
| Governance exposure | No | 11 of 15 |
| Strategy ownership | Limited | Common |
| External visibility | Low | 9 of 15 |
| Executive network | Limited | Common |
| Advanced qualification | Yes (MBA) | Moderate frequency |
Credentials and transformation-delivery depth.
Strategy ownership and governance exposure.
Selected reference: Jane Smith, current CIO. The goal is translation, not imitation.
Transformation background, strategy ownership, governance, executive exposure, external visibility.
Exact qualification, exact employers, exact industry, exact timeline.
Programme Director → Technology Director → Deputy CIO → CIO
Senior Programme Delivery Lead → Head of Technology Delivery → Technology Director / GM Technology → Deputy CIO → CIO
Current role.
Broadens scope from programme delivery to a full delivery function; first real budget ownership.
Enterprise-level scope; the point to actively pursue strategy ownership and a governance seat.
Full executive-team exposure; network-building becomes the dominant lever here.
Destination.
| Route | Speed | Risk | Leadership gain | Network gain |
|---|---|---|---|---|
| A: Internal Enterprise Lower transition risk, existing credibility. Risk: current employer may not provide true strategy ownership. | Moderate | Low | Moderate | Low |
| B: External Director Move Fastest scope increase, stronger title. Risk: title inflation without real authority. | Fast | High | High | Moderate |
| C: Consulting Leadership Network expansion, reputation, cross-industry visibility. Risk: weaker direct enterprise ownership. | Moderate | Moderate | Low | High |
Enterprise responsibility, permanent team leadership, material budget authority, strategic decision-making, executive reporting.
Governance participation, vendor/commercial responsibility, roadmap ownership.
Broader industry exposure, external visibility.
Don't accept the next role unless it gives you at least 3 of these 5: enterprise strategy ownership · meaningful budget responsibility · direct executive reporting · permanent team leadership · governance or steering-committee exposure.
Credential Capital (71) is already ahead of Leadership, Network and Reputation. Another qualification would deepen an existing strength rather than close the binding gap.
Avoid a larger programme role if it increases scale and salary but not strategy ownership, budget authority, governance, or executive responsibility.
Do not optimise for connection count. Prioritise the specific relationship categories in Move 2 above.
Enterprise scope in the current employer (major) · governance exposure concurrent with the next role (major) · early executive-network building (moderate) · one move that closes two or more gaps at once (major).
Another delivery-only role (major) · delaying executive relationships (major: this gap compounds over years, not months) · over-investing in qualifications (minor) · staying in a role after scope stops expanding (moderate).
Current answer: no major qualification recommended right now. Credential Capital (71/100) is already ahead of Leadership and Network, so an additional credential would not address the binding constraint.
Major financial institution, government department, health network, large regulated enterprise.
Senior titles without authority, delivery-heavy roles without strategy ownership, employers where executive technology decisions are centralised elsewhere.
Enterprise scale, active transformation agenda, existing governance structures Jordan can join.
If Head of Technology Delivery doesn't lead to real strategy ownership within 18 months, Route B or C becomes primary, not a backup.
Relationship capital compounds over years, not months. Starting in month one matters more than any single action.
Patterns may differ for smaller organisations or other cities, so treat the route as indicative, not fixed.
Career history, education, certifications.
Leadership scope, market fit, route timing.
Network depth, external reputation, future employer opportunities.
This measures evidence quality, not success probability.
Fact = confirmed user data or external evidence. Benchmark = observed pattern in the comparison cohort. Inference = RolePathways interpretation. Recommendation = suggested action. Every major claim above traces back to one of these four.
You now have a target destination, a Pathway Score, identified gaps, a primary route, alternative scenarios, and a 90-day action plan. But the pathway will change as you act on it, as the market shifts, and as opportunities appear.
Does this role move me closer to my target?
I changed role. What changes?
What should I focus on now?
Pathway Blueprint = one-time strategic diagnosis. RolePathways Core / Accelerate = ongoing navigation. Next Pathway Review recommended in 30 days.