gathering and defining requirements for your next cms project
TRANSCRIPT
![Page 1: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/1.jpg)
Defining requirements for your next CMS project
> Anthony D Paul
![Page 2: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/2.jpg)
› Technical lead at Fathom (end-to-end; 5 years)
› User experience developer
› @anthonydpaul
Who am I…
![Page 3: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/3.jpg)
› High-level design process (refresher)
› Focus on requirements definition (importance, context, parts)
› Specific tools and methodologies(purpose, pros/cons, samples)
› Case study
› Determining tools for you
What we'll talk about
![Page 4: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/4.jpg)
Theory behind the design process
Lewin’s Equation
Behavior = function(Person, Environment)
› Simply build environment that elicits the desired behavior, right?
› Can identify the behavior
› No control over the person
![Page 5: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/5.jpg)
The more we know about our users, the more likely we are to meet their needs.
![Page 6: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/6.jpg)
High-level interactive process
RequirementsDefinition
(info gathering, specification
Production(design,
development)
Delivery(training, launch,
maintenance)
Testing
![Page 7: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/7.jpg)
High-level interactive process
Production(design, development)
Delivery(training, launch,
maintenance)
![Page 8: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/8.jpg)
High-level interactive process
RequirementsDefinition
(info gathering, specification
Production(design,
development)
Delivery(training, launch,
maintenance)
Testing
![Page 9: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/9.jpg)
Foundation of the end product
Derived from: Jesse James Garrett’s "The Elements of User Experience"
Design
Local Architecture
Global Architecture
Functionality
Objectives (users, business)
TANGIBLE
ABSTRACT
![Page 10: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/10.jpg)
What does that path look like?
Derived from: Liz Sanders’ "Co-Creation"
What itends up being
What itcould be
![Page 11: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/11.jpg)
What does that path look like?
Derived from: Liz Sanders’ "Co-Creation"
What itcould be
![Page 12: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/12.jpg)
Foundation of the end product
Design
Local Architecture
Global Architecture
Functionality
Objectives (users, business)
TANGIBLE
ABSTRACT
![Page 13: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/13.jpg)
3 main components
RequirementsDefinition
Audit Processing Spec
![Page 14: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/14.jpg)
3 main components
RequirementsDefinition
AskAudit
ThinkProcessing
DoSpec
![Page 15: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/15.jpg)
So, what do these break down into?
AskAudit
ThinkProcessin
g
DoSpec
› (Objectives)
› Wants & needs (user vs. client)
› Climate (competition & market)
› Content
› (Functionality)
› Stories (humanity)
› Behaviors ($$$)
› Global arch. (taxonomy)
› Local arch. (hierarchy)
› Design
![Page 16: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/16.jpg)
Tools we use to define them
AskAudit
ThinkProcessin
g
DoSpec
› (Objectives)
› Wants & needs (user vs. client)
› Climate (competition & market)
› Content
› (Functionality)
› Stories (humanity)
› Behaviors ($$$)
› Global arch. (taxonomy)
› Local arch. (hierarchy)
› Design
› Surveys & interviews
› Card sorting
› Make tools (paper prototypes & collages)
› Personas
› Usage scenarios (task flows)
› Mood board
› Sitemap
› Wireframes
› A/B tests
› Digital prototypes
Component Tools
![Page 17: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/17.jpg)
Card sort
› Purpose Determines high-level categorization preferences
› Method Stacks of paper, sticky notes, 3x5 cards (allowing write-ins)
› Analysis Put results into outline form or clouds
› Strengths Simple, cheap, quick, fun, foundational
› Weaknesses Content-centric (not tasks), may vary,surface characteristics (not use)
![Page 18: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/18.jpg)
Card sort
![Page 19: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/19.jpg)
Card sort
![Page 20: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/20.jpg)
Make tools
› Purpose Determine emotional needs, sometimes functionality
› Method Kit of materials, words, pictures
› Analysis Notes for inspiration, tabulated
› Strengths Easy, fun, high user involvement, candid
› Weaknesses Time consuming, hard to analyze, somewhat expensive
![Page 21: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/21.jpg)
Make tools
![Page 22: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/22.jpg)
Make tools
![Page 23: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/23.jpg)
Personas
› Purpose Confirm understanding of users (notes for an exam)
› Method Write a story, add photo, name, motivations, etc.
› Analysis N/A
› Strengths Central reference encourages role-playing, fun, cheap
› Weaknesses Somewhat difficult, not quick, contains assumptions
![Page 24: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/24.jpg)
Personas
![Page 25: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/25.jpg)
Personas
![Page 26: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/26.jpg)
Usage scenarios
› Purpose Maps personas to objectives, walks through step-by-step actions
› Method Write ideal (but real) task flows, identify entrances & exits
› Analysis Identify patterns across users, prioritize
› Strengths Effective for common actions, auditable
› Weaknesses Somewhat difficult, not quick, contains assumptions
![Page 27: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/27.jpg)
Usage scenarios
![Page 28: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/28.jpg)
Usage scenarios
![Page 29: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/29.jpg)
Mood board
› Purpose High-level look and feel pre-design
› Method Assemble colors, textures, photos, typefaces, adjectives, screenshots
› Analysis N/A
› Strengths Clear communication, focuses designers, puts users and brand in sync, auditable
› Weaknesses Somewhat abstract
![Page 30: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/30.jpg)
Mood board
![Page 31: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/31.jpg)
Mood board
![Page 32: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/32.jpg)
Sitemap (& task flow)
› Purpose High-level taxonomy, task flows, navigation
› Method Treed map of content (not necessarily pages)
› Analysis N/A
› Strengths Organized for production, gives scope, auditable
› Weaknesses Overwhelming for clients, difficult to strike balance of info
![Page 33: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/33.jpg)
Sitemap (& task flow)
![Page 34: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/34.jpg)
Sitemap (& task flow)
![Page 35: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/35.jpg)
Wireframes
› Purpose Local hierarchy, audit
› Method Non-designed layout of each page
› Analysis N/A
› Strengths First visual, tangible, controls scope, testable
› Weaknesses Difficult to balance design vs. utility, sometimes requires many pages
![Page 36: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/36.jpg)
Wireframes
![Page 37: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/37.jpg)
Wireframes
![Page 38: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/38.jpg)
A/B tests
› Purpose Prove success of specific deliverable
› Method Compare two or more versions (isolation vs. side-by-side)
› Analysis Scored and tabulated
› Strengths Definitive and arguable, quick, easy
› Weaknesses Limited to options, can be difficult to assemble/coordinate
![Page 39: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/39.jpg)
A/B tests
![Page 40: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/40.jpg)
Digital prototype
› Purpose Prove system before design
› Method Build site without design (entire or partial)
› Analysis Task assignments, testing protocols, bug tracker
› Strengths Both quantity and quality, closest to end product, relevant
› Weaknesses Expensive if discarded, similar to wireframes can be hard to explain utility vs. design
![Page 41: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/41.jpg)
Digital prototype
![Page 42: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/42.jpg)
Digital prototype
![Page 43: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/43.jpg)
Case study
› International student organization
› Composted content
› Brand new messaging
![Page 44: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/44.jpg)
Biggest challenges
› Content audit
› Many stakeholders/users
› Sitemap
![Page 45: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/45.jpg)
![Page 46: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/46.jpg)
As a testament to the newly organized and optimized content,
one month after launch saw a 1200% increase in average daily page hits (previously averaging 1,200/day, now reaching more
than 30,000/day).
![Page 47: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/47.jpg)
Determining your tools
› Project size (budget)
› Personal preference
› Client need & risk
![Page 48: Gathering and Defining Requirements for Your Next CMS Project](https://reader033.vdocuments.us/reader033/viewer/2022060205/55a1bc791a28ab85218b46cc/html5/thumbnails/48.jpg)
@anthonydpaul