How I work with institutions
Institutions can describe what a student sat through. Far fewer can state what a graduate can actually do. The work below is about closing that gap — defining capability, making it verifiable, and building the systems that carry it. Three practice areas, drawn from fifteen years in engineering and teaching and doctoral research on how technology professionals actually work.
Pick your starting point
- 01
Career-Readiness Systems
Who this is for
- Universities & colleges
- Career services & experiential learning
- Workforce boards & training providers
- Professionals in career transition
Most institutions can describe what a student sat through. Far fewer can state what a graduate can actually do.
This is the work of building that second answer — a shared definition of capability, the program architecture that produces it, and the evidence that stands behind it. The same expertise applies one-to-one, with professionals moving through a labor market that is rewriting its own job descriptions.
What I deliver
- Competency framework design
- A written, shared definition of what a graduate should be able to do, with agreed criteria for what counts as evidence
- Program architecture
- Mapping courses, internships and co-curricular experience to one vocabulary, so the gaps become visible instead of anecdotal
- Program evaluation
- Reading an existing career-readiness program as an activity system to locate the contradiction that is actually blocking it
- Career navigation coaching
- One-to-one and group programs for professionals moving into, within, or upward in technology
- 02
Digital Credentialing & Learner Records
Who this is for
- Registrars & academic records
- Credentialing & badging teams
- Continuing & professional education
- Standards & consortium working groups
A certificate of completion records attendance. A credential built properly carries its own evidence — the skills claimed, the criteria met, and a way for a third party to verify it without picking up the phone.
Portability and verification are largely solved problems now. What a credential signifies still depends entirely on how the underlying skill was assessed, and that is where the design work lives.
What I deliver
- Credential architecture
- What each credential claims, what evidence it requires, and how an outside party verifies it unaided
- Comprehensive Learner Record planning
- Scoping a CLR against what your institution can genuinely assess and maintain, not against the demo
- Badge program design
- Assessment criteria first, platform second
- Standards evaluation
- Open Badges, CLR and the 1EdTech specifications weighed against your constraints rather than a vendor's roadmap
- 03
Technology Strategy & Enablement
Who this is for
- Institutional IT & leadership
- Teams adopting new platforms
- Organizations post-implementation
- Non-technical leadership teams
Most technology investments underperform because the strategy was wrong, not the technology. And most of the rest underperform because nobody taught anyone to use them well.
I work on both halves — the architecture decision and the capability that has to exist afterward for it to matter.
What I deliver
- Technology roadmaps & architecture reviews
- Phased plans grounded in operational reality rather than vendor sequencing
- Cybersecurity governance for educational institutions
- Policy, risk and practice matched to actual exposure
- AI readiness assessment
- Where it fits, where it does not, and what has to be true before it does
- Training & technical mentorship
- Cloud, data, security and development, built around your tools rather than generic courseware
- Certification pathways
- Structured routes through AWS, cybersecurity and data credentials
Book a call
Thirty minutes, no charge — bring the problem you are actually trying to solve.
Book a call →How I work
- Diagnose
- Start with the real problem, not the symptoms — where you are, where you need to be, and what is actually in the way.
- Design
- Build a strategy or program tailored to your context: your people, your constraints, your timeline. No off-the-shelf playbooks.
- Deliver
- Execute hands-on. Training, roadmap or coaching engagement — built alongside your team rather than from a distance.
- Sustain
- Transfer knowledge so it sticks. Every engagement is designed so your team keeps momentum after I step away.
Futures Change Laboratory
Futures Change Laboratory is a remote lab for workforce change — and where the engagements on this page actually run.
The work is preparing today's workforce for tomorrow's roles: naming what people can already do, what the work is about to require, and how to close the gap between them. Remote by design, because the organizations that need it are distributed, and because capability is built across sessions rather than delivered in one.
Proven impact
Numbers are the short version of a longer story — fifteen years of people coached, systems shipped and programs that outlasted the budget cycle that funded them.
Professionals coached
Career changers and practitioners guided through advancement across web development, data analytics, cybersecurity and UX.
Technical projects evaluated
Hands-on review across full-stack, data science, fintech and security — deep pattern recognition of what works.
Courses designed & delivered
Online and on-site programs spanning cloud, AI, cybersecurity, web development and technical project management.
Years in technology
From enterprise engineering and QA to cloud architecture, full-stack development and executive technology strategy.
Oxford executive programmes
Advanced study in AI, cybersecurity leadership, algorithmic trading, enterprise strategy and entrepreneurship at Saïd Business School.
Common questions
- What does an educational technologist do?
An educational technologist designs the systems that connect learning to work: career-readiness programs, competency frameworks and digital credentialing platforms that institutions run at scale. In practice that means career-readiness systems, digital credentialing and learner records, and technology strategy and enablement.
- Do you work with institutions or with individuals?
Both. Engagements run with organizations scaling tech teams, universities and training programs, HR and talent leaders, and leadership teams modernizing their technology — and one-to-one with professionals in career transition or building technical skills.
- What is a competency framework and why would an institution need one?
A competency framework is a written, shared definition of what a graduate should be able to do — broken into specific skills, each with agreed criteria for what counts as evidence. It is not a curriculum and not a course list. It is the vocabulary underneath both.
Institutions need one because without it, "career-ready" means something different in every department, and the institution cannot state what its own degree signifies in skill terms. A transcript answers what a student sat through. Employers are asking what a student can do. A framework is what lets you answer the second question with the rigor you already apply to the first.
It also makes everything downstream possible. You cannot measure, credential, or improve a skill you have not defined. Once the definitions exist, courses, internships, co-curriculars, and assessments can all map to the same vocabulary — and the gaps become visible.
- How is a digital credential different from a certificate of completion?
A certificate of completion records attendance. It says a person finished something. It rarely says what they can do, and there is usually no way for an outside party to check it without contacting the issuer.
A digital credential carries its evidence with it. Built properly, it holds machine-readable metadata: the specific skills claimed, the criteria that had to be met, who issued it, when, and often a link to the work itself. A third party can verify it without a phone call, and it belongs to the learner rather than living inside an institution's system.
Portability and verification are largely settled. What a credential signifies still depends on how the underlying skill was assessed — an open question the community of practice is working through together, since the standards are young and practice is still catching up to them. That is where the design work lives.
- What does an engagement typically look like?
Four stages: diagnose the real problem rather than the symptoms; design a strategy or program tailored to your people, constraints and timeline; deliver hands-on alongside your team; and sustain it by transferring knowledge so momentum continues after I step away.