Defining requirements for your next CMS project

> Anthony D Paul

› Technical lead at Fathom (end-to-end; 5 years)

› User experience developer

› @anthonydpaul

Who am I…

High-level interactive process, gathering & defining requirements, breakdown of tools & purpose, samples

High-level interactive process

High-level interactive process

RequirementsDefinition

(info gathering, specification

High-level interactive process

RequirementsDefinition

(info gathering, specification

Production(design,

development)

High-level interactive process

RequirementsDefinition

(info gathering, specification

Production(design,

development)

Delivery(training, launch,

maintenance)

High-level interactive process

RequirementsDefinition

(info gathering, specification

Production(design,

development)

Delivery(training, launch,

maintenance)

Testing

High-level interactive process

RequirementsDefinition

(info gathering, specification

Production(design,

development)

Delivery(training, launch,

maintenance)

Testing

High-level interactive process

Production(design, development)

Delivery(training, launch,

maintenance)

Testing

High-level interactive process

RequirementsDefinition

(info gathering, specification

Production(design,

development)

Delivery(training, launch,

maintenance)

Testing

3 main components

RequirementsDefinition

3 main components

RequirementsDefinition

Audit

3 main components

RequirementsDefinition

Audit UX

3 main components

RequirementsDefinition

Audit UX Spec

3 main components

RequirementsDefinition

AskAudit

AnalyzeUX

ApplySpec

So, what do these break down into?

AskAudit

AnalyzeUX

ApplySpec

So, what do these break down into?

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

So, what do these break down into?

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

So, what do these break down into?

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

› Global (taxonomy)› Local (hierarchy)

Tools we use to define them

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

› Global (taxonomy)› Local (hierarchy)

Component Tools

Tools we use to define them

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

› Global (taxonomy)› Local (hierarchy)

› Ask› Brainstorm

Component Tools

Tools we use to define them

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

› Global (taxonomy)› Local (hierarchy)

› Ask› Brainstorm

› Personas› Scenarios

Component Tools

Tools we use to define them

AskAudit

AnalyzeUX

ApplySpec

› Wants & Needs (user vs. client)› Climate (competition & market)› Content

› Stories (humanity)› $$$

› Global (taxonomy)› Local (hierarchy)

› Ask› Brainstorm

› Personas› Scenarios

› Sitemap› Flat wireframes

Component Tools

Each tool explained

› Ask surveys/interviews, e.g.quality answers

› Brainstorm card sorting, e.g.refined experiment

› Personas motivationsfilling in the blanks

› Scenarios common tasks & recycle ideal vs. realistic

› Sitemap content flowthorough vs. friendly

› Flat wireframes audit & visual priority design vs. utility

Comprised ofTools Challenges

A/B Test

Card Sort

Persona

User Scenario

Sitemap (& task flow)

Flat Wireframe

Determining your tools

› Project size

› Personal preference

› Client need

Thank you!

@anthonydpaul