Downloaded 27 times
![Refinement / Copy / Final Visual Design / Robust Testing Production Build / Reviews / Design Team Sign Offs
Product Team meets - Product Team meets -
Design meeting with Hand off to
Product Marketing, Product Team production,
Engineering, and Approval cycle here engineering and
Usability to review operations mode of
recommendations the product cycle
Detailed Product
testing - both for
functionality and
specific content and
visual design iteration cycle
iteration cycle
Design works w i t h
gn team Usability to provide Design team Final functionality &
storms, iterates prototype and presents visual design signoff
collaborates on guidance of what Refine Visual wireframes a n d User Ed. delivers all - Production
l representation Visual Design Experience priorities of direction, copy, mockups to Help text and - Engineering
nctionality and exploration, Design team discovery shoul d user instructions, production with full associate d - QA
en design s copy writte n review Visual be - i.e. business help and UI set of style specs screenshots a n d - Partner (if applicable)
can begin while and finetuned direction constraints, components as [font size & color, specs t o - Usability
flow a n d technical necessary line spacing, Production - Creative Director
ionality is constraints, colors, images, - Product Marketing
ing optional versions to links, etc] - VP (as necessary)
test
Production receives Production builds
approved mockups site and features
and works w i t h working wi t h
Design on product Engineering as
area as needed applicable
Engineering informs
Design if there are
changes, issues w i t h
planned functionality
15](https://image.slidesharecdn.com/20110331nashvilleuxslideshare-110426165529-phpapp01/75/Nashville-UX-Meetup-27-2048.jpg)
Uploaded byKaren McGrane
Nashville UX Meetup
This document appears to be a presentation on information architecture and content strategy. It includes: 1. An introduction from Karen McGrane from Bond Art + Science. 2. Several slides about information architecture, visual design, interaction design, and how they relate to content and user experience. 3. Slides discussing why content strategy is important and how it has changed from the past to now. 4. Slides showing how information architecture, user experience, content management, technology, marketing, and content strategy relate to each other. 5. Additional slides discussing topics like naming pain points, defining processes, current site audits, and more in relation to content strategy.
More Related Content
Nashville UX Meetup
- 1. Hi! I’m Karen McGrane from Bond Art + Science @karenmcgrane 1
- 2. Concept ruthlessly stolenfrom Heather Champ @hchamp Via Flickr User swirlspice under a Creative Commons License 2
- 3.
- 4.
- 5.
- 6. INFORMATION ARCHITECTURE VISUAL DESIGN 4
- 7. INFORMATION ARCHITECTURE VISUAL DESIGN INTERACTION DESIGN 4
- 8. CONTENT? INFORMATION ARCHITECTURE VISUAL DESIGN INTERACTION DESIGN 4
- 9.
- 10.
- 11. FROM TO Static Dynamic Centralized Decentralized Walled Social Costly Cheap Geeky Mainstream 7
- 12.
- 13.
- 14. USER EXPERIENCE Information Architecture 8
- 15. USER EXPERIENCE Information Architecture Content Management 8
- 16. USER EXPERIENCE Information Architecture Content Management TECHNOLOGY 8
- 17. USER EXPERIENCE Information Architecture Social Media Content Marketing Management TECHNOLOGY 8
- 18. USER EXPERIENCE Information Architecture Social Media Content Marketing Management MARKETING TECHNOLOGY 8
- 19. USER EXPERIENCE Information Architecture CONTENT STRATEGY Social Media Content Marketing Management MARKETING TECHNOLOGY 8
- 21. NAMING A PAINPOINT. 10
- 22.
- 23.
- 24.
- 25. Current Site Audit Stakeholder& Competitive & User Interviews Market Research Vision Insight Design Development QA Requirements IA Design Creative Design Usability Testing Post Launch Paper Prototype & Creative Comps Analytics Report Test, Measure, and Optimize
- 26. User Experience DesignProcess: Critical Path Kickoff Project Initiation Initial Design Cyc l e Design Iteration / Testing / Itera Meeting Project is Product Marketing Prod. Marketing does P&L, content evaluation, Product Team meets - inititated by Product creates materials that describe needs, goals, Marketing with Prod. Mktg. feeds team Design presents functional objectives, dependencies, partnerships, user flow, potential user Program business issues and any other relev a n t any results from Marke t Management scenarios and high level content or functionality issues, pulls together Resear c h screens need e d cross-functional tea m Approval cycle h e r e Feasability Studies / Field Resear c h Expert advice on Usability What do Users w a n t previous research a n d feedback cyc l e How do they want to do it Meeting new research need e d (Usability Conceptual Phase) (Usability 2nd Phase) coordinated by Program feedback cy Management UE Team member Create D e s i g n assigned to Spec/Creative Rapid prototype for Experience Design project Brie f proof of concept attends meeting UE Team Material is from and early testing w / brainstorm with Initial concept MRP/PRD and Early functionality usability brainstorms wit h Takes input from Usability - led by brainstorming notes designs and all members as project team Product Marketing to and other definitions of Could be paper UE Team member assigned related to UI member collect and gather requirements, distills pages needed for prototype, functional to project design requirements and info, looks at developed static HTML, Flash what's the best understand competitive functionality interaction, Receives Requirements scenario fo r competitive landscape landscape, rev i e w s Mockups/ Document use r s scope in context of Wireframes as Needs: network and sit e image maps List of team precedenc e members, contact info, initial schedule, approval process Initial exposure to (people) scope of design and functionality HTML Assess techn i c a l limitations and alternatives Engineering Engineering might begin coding work from initial functionality spe c s Credits: Erin Malone: Designed for AltaVista November 10, 2000 15
- 27. Refinement / Copy/ Final Visual Design / Robust Testing Production Build / Reviews / Design Team Sign Offs Product Team meets - Product Team meets - Design meeting with Hand off to Product Marketing, Product Team production, Engineering, and Approval cycle here engineering and Usability to review operations mode of recommendations the product cycle Detailed Product testing - both for functionality and specific content and visual design iteration cycle iteration cycle Design works w i t h gn team Usability to provide Design team Final functionality & storms, iterates prototype and presents visual design signoff collaborates on guidance of what Refine Visual wireframes a n d User Ed. delivers all - Production l representation Visual Design Experience priorities of direction, copy, mockups to Help text and - Engineering nctionality and exploration, Design team discovery shoul d user instructions, production with full associate d - QA en design s copy writte n review Visual be - i.e. business help and UI set of style specs screenshots a n d - Partner (if applicable) can begin while and finetuned direction constraints, components as [font size & color, specs t o - Usability flow a n d technical necessary line spacing, Production - Creative Director ionality is constraints, colors, images, - Product Marketing ing optional versions to links, etc] - VP (as necessary) test Production receives Production builds approved mockups site and features and works w i t h working wi t h Design on product Engineering as area as needed applicable Engineering informs Design if there are changes, issues w i t h planned functionality 15
- 28. An Example LEGEND MILESTONE DELIVERABLE IDEA REVIEW CHECKPOINT Product / Software / Web Design Process Guide KEY MEETING INFORM PHASES concept discover definition refinement developmen conceptual MILESTONES start concept approval proposal approval and scheduling design review PRD approval UI design approval committed schedule Communicate business needs Communicate business needs Brand Positioning Review Promotional & Marketing Needs Business developm & brand identity & brand identity { Mockups to marke Note: In some companies these roles are business owners encompassed by one person Collect team input Product Roadmap Promotion plan Describe problem or needs, Develop strategic rationale, business case, proposed solution, and benefits. financial analysis, policy considerations, implementation plans. Research: Solicit input from Business owners/ Point release plan product Gather information for and brands - contact other associated stakeholders (legal, customer support, international) manager create the Concept Document Gather supporting market research, etc. Write Draft PRD and Review Gather information for and create the Deliverables: ROLES Proposal Document Project kickoff Product Requirements Document Review user feedback on previous product Refine design concepts (PRD) Wireframes and navigation maps UI's and analyze competitive products. (authored by a { ui/id/ia Develop navigation model and Product Manager) Product prototype, e.g. paper, HTML, director, or flash refine scenarios design Provide input for level of effort UI Design Approval or two people. i.e. ui may do user research or visual designers may do ia, etc. and Idea Deliverable: Deliverable: Deliverable: Define personas, usage scenarios, user Proposal Templates Concept goals, and perform task analysis I T E R AT I O N S I T E R AT I O Document Document Concept Design Review & Develop usage scenarios this step Navigation and/or design concepts Concept and / or may be (authored by Note: In some companies these roles are blended into one optional Design UI / ID / IA Design) Provide input for level of effort Visual design explorations Refined Visual design explorations Art direction Materials Leads brainstorming Concept (authored by visual Prototype blended design design team) Provide input for level of effort UCD research cont'd. (i.e. paper prototyping, Competitive usability testing Prototype usability test Prototype testing participatory design, field studies, surveys, etc. Define personas, usage scenarios, user user goals, and perform task analysis. research production Provide input for level of effort credits Design based on earlier maps created by various UI design teams at America Online Incorporated. Revised and edited by Erin Malone, September 2003 for the AIfIA. 16
- 29. DELIVERABLE IDEA REVIEW CHECKPOINT MILESTONE KEY MEETING INFORM inement development launch preparation post launch RD UI design committed visual design beta launch pproval approval schedule approval Review Promotional & Marketing Needs Business development / partnering Mockups to marketing Product Roadmap Promotion plan Point release plan L Evangelize A Post mortem U Wireframes and navigation maps Final product Product prototype, e.g. paper, HTML, director, or flash Begin writing functional spec specification Design fidelity checks and bug fixes UI maintenance & handoff to UI Design Approval UI Revisions based on testing build team N Deliverable: I T E R AT I O N S Templates I T E R AT I O N S & Navigation C (authored by UI / ID / IA Design) Refined Visual design explorations Art direction Visual Design Approval Handoff to build team Visual maintenance H Competitive usability testing Prototype usability test Prototype testing Write/update test plans for final usability Usability test release product capture issues for next release Focus Group, Field Studies, Survey Analysis, etc. Execute visual design Build/publish Build HTML QA 16
- 30. PHASE 1 PHASE 2 Design Analysis Design Solutions TSDesign User Experience Audit SM Product Strategy and Product Design Strategy Blueprint* Technology Audit description: • an expert design analysis from the user’s perspective description: • define ‘what the product should be’ and ‘how it 1 understand 2 investigate 3 define users 4 qualify features should work’ benefits: corporate mission persona user profiles user, feature, objective matrix • benchmarks the effectiveness of your site based upon stated benefits: core competencies • the achievement of clearly articulated, agreed- user profiles business objectives for the site and your users corporate goals • analyzes the design of the site to find out if the benefits of use upon and aligned mission, core competencies, culture and values User Personae & corporate goals, and objectives for the site are actually being delivered Profiling Module speculate & + interviews SM skills and methodologies • the articulation and understanding of your users, • recommends methods for substantially improving your users experiences and meeting future business objectives their needs and and your business objectives for knowledge capital and experience (UP&P) innovate people, processes & technology establishing and extending relationships with each one stakeholders and initiatives Intentional User Experience table • TSDesign Analysis FrameworkSM • the definition of the organizational resources enterprise-wide challenges competitive and comparative analysis experience brief: 1 Delivery of User Benefits The intended value the organization required to build and maintain the site Internet objectives strategy story and positioning delivers to users and customers through its site. • the creation of a detailed blueprint for design or customers and users redesign: The sequence of questions, prompts, and results - site organization (footprint) competitive landscape 2 Transaction Flow that make up a task. - useful and usable features and functions for the users * workbooks not shown The degree to which a site affords the user to easily - descriptions of intended functionality scope or 3 Navigation & Hierarchy navigate the environment and efficiently locate rele- - messaging strategy rescope relationship 5 7 vant content. The representation and support of the identity, • the receipt of a phased implementation plan with associated costs innovate 6 refine describe 4 Visual Language brand and information architecture through visual elements and overall style. new ideas new footprint and reclustered content Product Strategy Blueprint/Functional Description existing Audit comments: and new • Users arriving at the front page of the site may not understand what information is there for them. technology • The names of the sections do not give users a path to follow to find the informa- tion they need. • No specific path has been established for each user type. Users must use their best judgement to find the information they’re looking for and often may not be successful. Identity and Visual Language Audit Visual Identity Systems visual language research description: description: • By collecting and reviewing print, other tangible artifacts and • establish, with the client, a shared Web sites your company creates and disseminates, and understanding and common language for corporate standards (if they exist) we can then distill the basis visual design and how it effectively for the visual language to be developed that is consistent with communicates the brand the company's identity and product brands. This work is • define a visual language for the site continued in the Visual Systems Design phase. - logo, logotype systems - typography - grid system - color palette - imagery style and usage benefits: • provides the visual language components with which to build the interface 17
- 31. ation ng Interaction Design Information Architecture Interface Design Production description: description: description: description: echnology to • create seamless and consistent transaction flow • define site hierarchy • using the components, defined in the Visual Systems • create sample HTML files to illustrate page layout ith client's • define widgets and technologies to best support • define navigation scheme Design Phase, create design styles for each page-type and design styles the features and functionality • define hierarchy of information on pages needed to support interaction, navigation and hierarchy • deliver and present documentation s • identifies content workflow and organizational • apply these design styles to page schematics • Interface QA / training ical teams responsibilities and resources usability testing usability testing process overviews site maps schematic drawing digital sketches HTML interface files online styleguide innovate page schematics & content development Discount Usability scription: testing to discover usability problems to provide information to team to help detect and resolve transaction flow and navigation and techinal problems 17
- 32. THE CONTENT STRATEGYPROCESS 18
- 33. 1. THINK BEYONDTHE TEMPLATE. 19
- 34. This page wasredacted so I don’t get yelled at by lawyers. Honestly, doesn’t that sound awful? You wouldn’t want that to happen to me, right? If you’re really curious this was a persona. It looks pretty much like every other persona you’ve ever seen. So just imagine one of those.
- 35. This page showeda competitive audit. If you want to recreate the experience for yourself, go click around to some other websites and write down a few comments about whether they’re any good or not.
- 36. This here isa series of moodboards that show an approach to creating a design system, including photography, color palettes, and typography.
- 37. Sigh. Okay, thispage shows some sketching exercises we did. Except apparently no one on the team could figure out how to operate a pen, so somehow “sketches” wound up meaning “wireframes made with wavy lines and handwritten fonts.” I’m embarrassed just admitting that. Can we go back to talking about how your content sucks?
- 38. This page showeda wireframe. The lines were all straight and the font was Arial. Master of my craft, here.
- 39. We opted togo live with the existing content. 25
- 40. Buy-in for thatdecision stretched to the highest levels of the organization. 26
- 41. We knew thecontent sucked. We just believed there was nothing we could do about it. 27
- 42.
- 43.
- 44. Within an hour,the angry calls started. Client received hundreds of angry calls from franchisees the first day. http://www.flickr.com/photos/schoppa/3148751414 28
- 45. Within an hour,the angry calls started. Client received hundreds of angry calls from franchisees the first day. Complaint call volume held steady over the next week as people called back to check on status. http://www.flickr.com/photos/schoppa/3148751414 28
- 46. Within an hour,the angry calls started. Client received hundreds of angry calls from franchisees the first day. Complaint call volume held steady over the next week as people called back to check on status. The client team was unprepared to make quick changes to the content, and their slow response just added fuel to the fire. http://www.flickr.com/photos/schoppa/3148751414 28
- 47. Within an hour,the angry calls started. Client received hundreds of angry calls from franchisees the first day. Complaint call volume held steady over the next week as people called back to check on status. The client team was unprepared to make quick changes to the content, and their slow response just added fuel to the fire. Site had to be rolled back to the previous version while they came up with a plan to update the content. http://www.flickr.com/photos/schoppa/3148751414 28
- 48.
- 49. 7000 pages. 29
- 50.
- 51. 7000 pages. 45 people. Sixweeks. 29
- 52. 7000 pages. 45 people. Sixweeks. 5400+ hours. 29
- 53. 7000 pages. 45 people. Sixweeks. 5400+ hours. 29
- 54. 7000 pages. The upside is that the second 45 people. launch was very successful. Six weeks. Still, I can't say that I'd choose to 5400+ hours. do it that way again. 29
- 55. HOW TO THINKPAST TEMPLATES 30
- 56. HOW TO THINKPAST TEMPLATES _Talk about why it’s important to provide great content. Even when people don’t want to listen. 30
- 57. HOW TO THINKPAST TEMPLATES _Talk about why it’s important to provide great content. Even when people don’t want to listen. _Get content in the project plan, even if you’re not responsible for it. 30
- 58. HOW TO THINKPAST TEMPLATES _Talk about why it’s important to provide great content. Even when people don’t want to listen. _Get content in the project plan, even if you’re not responsible for it. _Scare people with the “giant spreadsheet of terror.” 30
- 59. HOW TO THINKPAST TEMPLATES _Talk about why it’s important to provide great content. Even when people don’t want to listen. _Get content in the project plan, even if you’re not responsible for it. _Scare people with the “giant spreadsheet of terror.” _Prototype and test wireframes and designs with best and worst case example content. 30
- 60. HOW TO THINKPAST TEMPLATES _Talk about why it’s important to provide great content. Even when people don’t want to listen. _Get content in the project plan, even if you’re not responsible for it. _Scare people with the “giant spreadsheet of terror.” _Prototype and test wireframes and designs with best and worst case example content. _Start content migration early: first step, not the last. 30
- 61. 1. THINK BEYONDTHE TEMPLATE. 2. EVALUATE CONTENT QUALITY. 31
- 62. From Flickr User2493™ 32
- 63.
- 64. I’m better atthinking about abstract relationships between content types, classification frameworks, metadata elements, than I am at looking at the specifics of content. Dan Brown, Letter to a Content Strategist 34
- 67. This page showeda video. You’re not going to be able to see it on Slideshare, so I took it out. It contained the phrase “fecal matter,” which to me is more offensive than saying “sh*tstorm.” Mythbusters, Polishing a Turd 37
- 68.
- 69. From Flickr User2493™ 39
- 70. HOW TO EVALUATEQUALITY 40
- 71. HOW TO EVALUATEQUALITY _Don’t just inventory: analyze your content. Don’t just look at what you have, assess whether it’s any good. 40
- 72. HOW TO EVALUATEQUALITY _Don’t just inventory: analyze your content. Don’t just look at what you have, assess whether it’s any good. _Have a strategy for how to persuade stakeholders that your approach is valid. 40
- 73. HOW TO EVALUATEQUALITY _Don’t just inventory: analyze your content. Don’t just look at what you have, assess whether it’s any good. _Have a strategy for how to persuade stakeholders that your approach is valid. _Conduct a gap analysis to compare what you have to what you need. 40
- 74. HOW TO EVALUATEQUALITY _Don’t just inventory: analyze your content. Don’t just look at what you have, assess whether it’s any good. _Have a strategy for how to persuade stakeholders that your approach is valid. _Conduct a gap analysis to compare what you have to what you need. _You can usability test content too. 40
- 75. 1. THINK BEYONDTHE TEMPLATE. 2. EVALUATE CONTENT QUALITY. 3. PLAN FOR CONTENT CREATION. 41
- 76. WRITERS ARE LIKEDEVELOPERS. THEY WORK BETTER WITH DIRECTION. 42
- 77. Logo Features Browse Our Sites About Us Sign Up Login Support Feature Name Duis autem vel eum iriure dolor in hendrerit in vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Find out more about: Feature Name | Feature Name | Feature Name | Feature Name | Feature Name | Feature Name 43
- 78. Logo Features Browse Our Sites About Us Sign Up Login Support Feature Name PUT PRODUCT DESCRIPTION HERE esse molestie consequat, vel illum dolore eu feugiat nulla facilisis at vero eros et accumsan et iusto odio dignissim qui blandit praesent luptatum zzril delenit augue duis dolore. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat. Ut wisi enim ad. Find out more about: Feature Name | Feature Name | Feature Name | Feature Name | Feature Name | Feature Name 44
- 79.
- 80.
- 81. HOW TO SPECCONTENT 46
- 82. HOW TO SPECCONTENT _Connect back to the overall brand and messaging architecture. 46
- 83. HOW TO SPECCONTENT _Connect back to the overall brand and messaging architecture. _Direct the writer to appropriate source materials, both online and offline. 46
- 84. HOW TO SPECCONTENT _Connect back to the overall brand and messaging architecture. _Direct the writer to appropriate source materials, both online and offline. _Guide selection of images, videos, and data visualizations, if needed. 46
- 85. HOW TO SPECCONTENT _Connect back to the overall brand and messaging architecture. _Direct the writer to appropriate source materials, both online and offline. _Guide selection of images, videos, and data visualizations, if needed. _Indicate how often each content element should be reviewed, edited, or deleted. 46
- 86. HOW TO SPECCONTENT _Connect back to the overall brand and messaging architecture. _Direct the writer to appropriate source materials, both online and offline. _Guide selection of images, videos, and data visualizations, if needed. _Indicate how often each content element should be reviewed, edited, or deleted. _Provide direction across channels: web, email, social. 46
- 87. 1. THINK BEYONDTHE TEMPLATE. 2. EVALUATE CONTENT QUALITY. 3. PLAN FOR CONTENT CREATION. 4. DON’T FEAR NEW ROLES. 47
- 88.
- 89.
- 90.
- 91. We don't needa Any backend project manager. The developer should be developers should be able able to crank out some to manage themselves. HTML. HTML is easy. Why do we even I don’t get why we need different roles need a content strategist. for interaction and Writers can make visual design? spreadsheets. 51
- 92. Here I wentoff on a little rant about roles on projects. I try to avoid talking about roles and job titles; I agree with Jared Spool that we should be talking about skills. I was actually afraid to talk about this but it seemed to go over well. I might try talking about it again someday.
- 93. FIRST: YOU WILL ADVOCATE FORCONTENT.
- 94. SECOND: YOU WILL USEYOUR NEW CONTENT STRATEGY TOOLS.
- 95. THIRD: YOU WILL PARTNERWITH A CONTENT STRATEGIST.
- 96.
Editor's Notes
- #2 I’m not really a content strategist, I’m an information architect\nSpent the past year talking about CS, why?\nGot here from tech writing, am a word person\n
- #3 \n
- #4 Yet the UX field seems to have a blind spot when it comes to content\nCollective delusion that what we make is templates and wrappers instead of a total experience, which includes content\nWe need to fix that. If you don’t think this needs fixing\n
- #5 We’re so comfortable with this collective delusion\nWhat’s changed?\n
- #6 We’re so comfortable with this collective delusion\nWhat’s changed?\n
- #7 We’re so comfortable with this collective delusion\nWhat’s changed?\n
- #8 We’re so comfortable with this collective delusion\nWhat’s changed?\n
- #9 \n
- #10 \n
- #11 What’s changed in the world that leads to needing content strategy? A lot.\n
- #12 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #13 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #14 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #15 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #16 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #17 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #18 TRANSITION:\nThings have changed, but the more they change, the more they stay the same.\nContent strategy reminds me of nothing so much as the early days of IA\nHelpful to remember a couple of things that we did right, things that are happening right now with CS.\n
- #19 Reminds me of a meeting that I had a couple of years ago.\n
- #20 Giving a label to a problem someone already has\nOr a task that someone is already doing\nIt sells itself, because you’re tapping into an unmet need\n
- #21 I’m a process junkie\n
- #22 \n
- #23 \n
- #24 To determine what web initiatives would create the biggest impact, we completed an assessment project with three components: \nA Market Overview to determine competitor best practices and industry benchmarks \nAnalytics of current site usage\nUsability Audit of the site with philosophy's target demographic performing tasks on the site\nDuring the design phase we continued with usability research, testing and optimizing the design.\nFinally we followed up with a post launch analysis to see how we did and provide further recommendations.\n \n
- #25 \n
- #26 \n
- #27 \n
- #28 Content strategy activities and deliverables get treated like a black box\nWe just expect great content to pop out at the end like magic.\nDoesn’t happen. Instead what you get is a shitstorm at the end of the process.\nTRANSITION:\nContent strategy deserves a process too, activities and deliverables\nYou can help, and you need to start talking about these things, even if you’re not a content strategist.\nThree things that you can do.\n
- #29 Asked for stories about content disasters\nFormer client contacted me about a problem\nI led the project\n
- #30 \n
- #31 \n
- #32 \n
- #33 \n
- #34 \n
- #35 \n
- #36 \n
- #37 Thought that when the hotels saw the shiny new templates, they would be so excited, it would be like Christmas Morning. They would be inspired to want to go play with their new toy and write some new content.\n
- #38 \n
- #39 \n
- #40 \n
- #41 \n
- #42 \n
- #43 Statement of work was for 25 templates.\n
- #44 Statement of work was for 25 templates.\n
- #45 Statement of work was for 25 templates.\n
- #46 Statement of work was for 25 templates.\n
- #47 Statement of work was for 25 templates.\n
- #48 Statement of work was for 25 templates.\n
- #49 Your job isn’t to deliver new layouts or new navigation categories. Your job is to deliver a better experience — which means better content.\n
- #50 Your job isn’t to deliver new layouts or new navigation categories. Your job is to deliver a better experience — which means better content.\n
- #51 Your job isn’t to deliver new layouts or new navigation categories. Your job is to deliver a better experience — which means better content.\n
- #52 Your job isn’t to deliver new layouts or new navigation categories. Your job is to deliver a better experience — which means better content.\n
- #53 Your job isn’t to deliver new layouts or new navigation categories. Your job is to deliver a better experience — which means better content.\n
- #54 \n
- #55 \n
- #56 \n
- #57 \n
- #58 \n
- #59 \n
- #60 \n
- #61 \n
- #62 \n
- #63 \n
- #64 \n
- #65 \n
- #66 \n
- #67 How many of you have ever written a functional spec, or have annotated your wireframes?\n
- #68 \n
- #69 \n
- #70 \n
- #71 \n
- #72 \n
- #73 \n
- #74 \n
- #75 \n
- #76 \n
- #77 Internecine warfare\nHandwringing\n
- #78 \n
- #79 \n
- #80 \n
- #81 \n
- #82 Roles are good, they keep people’s sphere of influence separate\nWatch movie credits\nRoles are good for our industry, they convey the magnitude of our efforts\n
- #83 \n
- #84 \n
- #85 \n
- #86 \n