Get notified when Mark publishes

Receive a notification each time a new blog post is published. You will receive a confirmation email to approve your email. Unsubscribe anytime.

Mark Smith

Mark Smith

· 4 min read

The project economy looks like the movies

Work is shifting from jobs to projects. Like filmmaking, teams assemble for a clear outcome, deliver, then disband.

The project economy looks like the movies
Share

The project economy looks like the movies

Watch the credits at the end of a film. Specialists come together for one production, deliver, then move on. That is where knowledge work is heading. Teams will be hired for outcomes, not headcount. Careers will compound through credits and networks, not tenure.

What’s changing#

Employers are organising around skills and measurable outcomes. Let’s look at insights from recent reports:

  • Microsoft’s latest Work Trend Index draws on 31,000 people, 31 countries and Microsoft 365 telemetry, and identifies a shift to skills-first, AI-enabled work patterns (Microsoft WorkLab, Work Trend Index hub).
  • The World Economic Forum survey of employers representing 14 million+ workers found that major workforce changes are planned, with jobs and skills evolving quickly (WEF Future of Jobs 2025).
  • LinkedIn’s data shows skills-first hiring can expand talent pools up to ~10x and that ~70% of the skills used in most jobs will change by 2030 (LinkedIn Economic Graph, Work Change Report 2025).

Why the movie industry is the template#

  • Studios → people and organisations needing something created. Fund outcomes.
  • Producers and directors → product owners and solution architects. Define scope, budget, and vision.
  • Casting → talent sourcing. Platforms that match skills to projects. LinkedIn, as well as others.
  • Credits → portfolios. Careers built on shipped work with metrics and references. (I plan to write more on this soon.)
  • Residuals → outcomes-based pay. This needs a lot more thought, but it will depend on your portfolio and personal network.
  • Hollywood careers → networked paths. Evidence from film labour markets (AJS study).

Why does this accelerate now?#

  • AI as capacity. Leaders are redesigning work so people and AI operate as a team (Microsoft WorkLab, follow-up analysis).
  • Skills-first economics. Skills-based search widens candidate pools and increases mobility (LinkedIn skills-first).
  • Market signals. “AI-literate” now appears across job ads, technical and non-technical.
  • Policy and protections. Global bodies are drafting standards for platform-mediated work, recognising its scale and risks (ILO standard-setting, draft conclusions; overview of Digital labour platforms). Human Rights Watch documents the prevalence and pitfalls of gig work in the US (HRW report).

What this means for you#

Permanent roles will still exist, but there will be a growing number of people taking on project-based work. Expect shorter cycles, clearer outcomes, and public proof of work. Your edge comes from a portable skills stack, verifiable credits, and the ability to drop into a team and deliver fast.

The skills to build now#

  1. Outcome portfolio
    Publish a portfolio that shows the problem, your role, actions, and measurable results for each project. Treat it like a showreel.
  2. AI fluency
    Design safe, measurable AI-assisted workflows. Show how you automated and the time or cost you saved. Employers now look for “AI-literate” candidates across functions.
  3. Skills-first signalling
    Make your skills machine-readable (Think AI recruitment) and mapped to target roles. Align with skills taxonomies used by marketplaces and HR tech.
  4. Project hygiene: the 4Ts
    Always clarify time, task, team, and transition. Define exit criteria and handover up front.
  5. Collaboration under pressure
    Operate with short feedback loops. Keep decisions, risks, and next actions visible.
  6. Commercial literacy
    Understand scopes, change orders, IP, confidentiality, usage rights, and warranties, and price for outcomes where sensible.
  7. Measurement and narrative
    Tie your contribution to live metrics. Tell the story in four beats: baseline, intervention, result, next step.
  8. Network maintenance
    Curate a lightweight network by skill and reliability. After each project, request a one-line, attributable reference.
  9. Ethics, privacy, and compliance
    Build simple checklists for data handling, accessibility, and bias. Apply them to every project.
  10. Learning velocity
    Maintain a tight learning plan aligned with pipeline demand. Drop what you will not use within 120 days.

30-day actions#

  • Ship a portfolio with your three strongest credits.
  • Rewrite your CV to a skills-first format with project metrics (skills-first guide).
  • Document one or more AI-assisted business processes/workflows with before-and-after numbers (practical tips).
  • Create a reusable one-page project charter using the 4Ts (background).
  • Ask three collaborators for a two-sentence reference you can quote.

Copilot-ready prompts#

Use these prompts in Microsoft 365 Copilot or your preferred tool.

Portfolio credit builder
“Turn the notes below into a 150-word project credit; structure: problem, role, actions, metrics, impact, link. Make metrics auditable. Notes: .”

Skills-first CV mapper
“From these credits, extract skills using common taxonomies. Map each skill to matching roles and list gaps to close in 120 days. Data: ”

Work is shifting to production. Portfolios beat positions, credits beat tenure. Build your showreel, tune your skills, and measure outcomes. When the next production starts, will your name be on the call sheet?


Mark Smith

Mark Smith

Principal AI Strategist · Microsoft MVP

Helping people build practical AI skill in the Intelligence Age.

Discussion

Comments

Loading the discussion for this post.

Loading

Leave a comment

Your email stays private. If it matches a Gravatar account, your public avatar can appear after the comment is approved.

Used only for reply notifications and optional Gravatar matching. Never displayed publicly.

Max 2000 characters0/2000

More from nz365guy

Artificial Intelligence

Building a DevOps team from AI agents on OpenCLAW

Ten AI agents, each owning a phase of the DevOps infinity loop, coordinated by an engineering-manager agent. How I built a development team that plans, builds, codes, tests, releases, deploys, operates, and monitors continuously.

· 15 min read
Artificial Intelligence

Hardening OpenCLAW on Azure after a live audit

A live audit of my OpenCLAW Azure VM found two critical gaps: no Azure-native VM backup and no Azure Monitor Agent. Here is what I fixed, what it cost, and what is still unproven.

· 13 min read
Artificial Intelligence

I found 268 plaintext secrets in my AI stack

Six weeks ago a security audit told me I had 268 plaintext secrets scattered across my AI agent platform. This week I closed out the migration that fixed it. Here is what I learned about credentials, AI agents, and the gap between what we build and what we secure.

· 15 min read