future-proofing your content strategy: how to plan for what you don't know you don't know
TRANSCRIPT
Future Proofing Your Content Strategy: How to Plan for What You Don’t Know
You Don’t KnowJoe Pairman
Consulting Practice Lead @mekon
As managers who areimplementing content strategies
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
Gaps in our awareness
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
teaching
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
teaching
tech assumptions
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
teaching
tech assumptions
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
teaching
tech assumptions
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
scope/cost/timeproblems
“acts of God”
teaching
tech assumptions
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
teaching
pre-mortem
tech assumptions
scope/cost/timeproblems
“acts of God”
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
teaching
pre-mortem
tech assumptions
scope/cost/timeproblems
“acts of God”
We know well
Business priorities
User requirements
Broad strategy
Project goals, processes, budget
We’re OK not knowing
Each project detail
How exactly to code and configure
the solution
Incidental hiccups