Solving Business Problems for Our Clients, Each Step of the Way

welcome Thursday, September 24, 2009

introductions IN WHICH WE AGREE UPON WHY WE ARE HERE Thursday, September 24, 2009

our founder: Jeffrey Zeldman photo: Adrian Q | ﬂickr: aquan Thursday, September 24, 2009

his book(s) DESIGNING WITH WEB STANDARDS (1st, 2nd, & soon 3rd Editions, + a few others) Thursday, September 24, 2009

our website Thursday, September 24, 2009

AIGA Mozilla Build-A-Bear United States Holocaust Memorial Museum Daily Kos e Today Show Georgetown University omson Reuters Greater Philadelphia Tourism & Marketing W3C Corporation Wordpress Krylon Paints Zappos our clients Thursday, September 24, 2009

our website Thursday, September 24, 2009

our events Thursday, September 24, 2009

so what? Thursday, September 24, 2009

why us? Thursday, September 24, 2009

why us? Mr. Cooksey asked us. We said yes. Thursday, September 24, 2009

why us? Mr. Cooksey asked us. We said yes. Why not us? Why not you? Thursday, September 24, 2009

why us? Mr. Cooksey asked us. We said yes. Why not us? Why not you? Not a pitch, but a conversation. Thursday, September 24, 2009

Thursday, September 24, 2009

ROBERT sales IN WHICH WE EXPLORE THE ETHICS OF SEDUCTION & BETTER LIVING THROUGH CHEMISTRY Thursday, September 24, 2009

ROBERT basic sales process Thursday, September 24, 2009

ROBERT basic sales process Project Planner Thursday, September 24, 2009

ROBERT basic sales process Project Planner Dialogue & Follow Up Thursday, September 24, 2009

ROBERT basic sales process Project Planner Dialogue & Follow Up Closing the Deal Thursday, September 24, 2009

the project planner ROBERT Thursday, September 24, 2009

dialogue & follow up ROBERT It’s all about communication. And coordination. Thursday, September 24, 2009

closing the deal A always B be C closing Thursday, September 24, 2009

ROBERT our values Thursday, September 24, 2009

ROBERT our values No spec work: nothing is free. Thursday, September 24, 2009

ROBERT our values No spec work: nothing is free. We pitch our people, principles, and process. Thursday, September 24, 2009

ROBERT our values No spec work: nothing is free. We pitch our people, principles, and process. Talk is cheap: share ideas freely. Thursday, September 24, 2009

ROBERT our values No spec work: nothing is free. We pitch our people, principles, and process. Talk is cheap: share ideas freely. One to one (or small group) conversation is priceless. Thursday, September 24, 2009

ROBERT client vendor chemistry Thursday, September 24, 2009

ROBERT client vendor chemistry Sometimes we say no (thank you). Thursday, September 24, 2009

ROBERT client vendor chemistry Sometimes we say no (thank you). Not every project is right for us. And vice-versa. Thursday, September 24, 2009

Carlisle Wide Plank Flooring “...we’ll treat ya to some magical wood.” - email from Client Thursday, September 24, 2009

ROBERT Mozilla Foundation Thursday, September 24, 2009

ROBERT Mozilla Foundation We went big (in scope). Thursday, September 24, 2009

ROBERT Mozilla Foundation We went big (in scope). ey came back and said smaller. Thursday, September 24, 2009

ROBERT Mozilla Foundation We went big (in scope). ey came back and said smaller. We went smaller. Thursday, September 24, 2009

ROBERT Mozilla Foundation We went big (in scope). ey came back and said smaller. We went smaller. ey said, “yes” but “involve the community in the process.” Thursday, September 24, 2009

DAVE project management IN WHICH WE DECIDE HOW WHO WILL DO WHAT WHEN & WHY Thursday, September 24, 2009

DAVE our pm philosophy Adapt classic project management approaches to web projects Waterfall can be agile Add some personality to the mix! Thursday, September 24, 2009

DAVE web project concepts Open minds = successful projects Dra timelines establish project timeframes Manage milestones “e Evolution Solution” - Focus on current phase + four weeks beyond Thursday, September 24, 2009

on waterfall & agile Predictability versus ﬂexibility DAVE All you got to do is talk, talk Thursday, September 24, 2009

on waterfall & agile Predictability versus ﬂexibility DAVE All you got to do is talk, talk Google Search: “Waterfall” Google Search: “Agile” Thursday, September 24, 2009

DAVE pm with personality Build the expectation. Become the consummate comedic professional. “Hi Tina, Tom, Kim, John and all the ships at sea. We’re nautical by nature ya know! :)” Thursday, September 24, 2009

DAVE Carlisle Wide Plank Flooring Established Communication, Mutual Trust and Respect Home made muﬃns, ohh so warm & tasty Change to planned technical assessment deliverable Altered project plan to meet Client needs Invited Tech lead to participate in CMS integration Thursday, September 24, 2009

DAVE Mozilla Foundation Open design process with Mozilla Community Utilized elements of Agile, Rapid Design and Waterfall to complete project tasks and maintain an “open” feel to the project Evolution of requirements vs. revolution of scope Thursday, September 24, 2009

KEVIN project definition IN WHICH WE CHOOSE THE PROPER STARTING FOOT & IN WHICH DIRECTION TO GO Thursday, September 24, 2009

project definition 100.00% 75.00% 50.00% 25.00% 0% Potential Baggage Thursday, September 24, 2009

KEVIN project definition: our goals Thursday, September 24, 2009

KEVIN project definition: our goals Identify the key players. Explore the communications dynamic. Immerse ourselves in the culture. Deﬁne the project. Thursday, September 24, 2009

KEVIN kickoff should establish... Thursday, September 24, 2009

KEVIN kickoff should establish... a high level of positive energy, the appropriate conceptual depth, a sense of humor, & unanticipated delight at our approach. Thursday, September 24, 2009

KEVIN stakeholder interviews By moing stakeholder interviews prior to kickoﬀ, you can spend less time on unknowns during the kickoﬀ and work at a better conceptual depth. Thursday, September 24, 2009

KEVIN priority card sorting game An exercise that assesses information priorities for an organization and quantiﬁes variations in priority between a client and a vendor, two departments in the same organization, two diﬀerent types of users, or any two groups. Thursday, September 24, 2009

step 1 KEVIN In advance, list all your topics on a set of index cards. Create a set for each participant. 15 topics is a good upper limit. Thursday, September 24, 2009

step 1 KEVIN In advance, list all your topics on a set of index cards. Create a set for each participant. 15 topics is a good upper limit. Topic 1 Topic 2 Topic 3 Topic 4 Topic 5 Topic 6 Topic 7 Topic 8 Thursday, September 24, 2009

step 2 KEVIN Arrange the group around the table so that a representative from each group is in an alternating seat. Ideally, no one should be sitting next to someone they work with. Thursday, September 24, 2009

step 3 KEVIN Ask each participant to sort their cards from highest to lowest priority, with the highest priority on the top and lowest priority on the bottom. Topic 1 Topic 2 Topic 3 Topic 4 Topic 5 Topic 6 Topic 7 Topic 8 Thursday, September 24, 2009

step 3 KEVIN Ask each participant to sort their cards from highest to lowest priority, with the highest priority on the top and lowest priority on the bottom. Topic 8 Topic 4 Topic 1 Topic 2 Topic 36 Topic Topic 7 5 Thursday, September 24, 2009

step 4 KEVIN Each participant must remove their 3 lowest priority cards from the group, place a hash mark in the corner of the card, and pass them to the person on their le. Topic 7 8 Topic 4 Topic Topic 1 Topic 23 Topic Topic 6 Topic 5 Thursday, September 24, 2009

step 4 KEVIN Each participant must remove their 3 lowest priority cards from the group, place a hash mark in the corner of the card, and pass them to the person on their le. Topic 7 Topic 8 Topic 1 Topic 23 Topic Topic 6 Topic 5 Topic 4 Thursday, September 24, 2009

step 4, variation KEVIN Prior to passing, allow each participant to “save” one card that can’t be lost, and to discard one card that is the least important. ese cards should then be designated as “save” or “remove,” and then set aside from play. Topic 7 8 Topic 4 Topic Topic 1 Topic 23 Topic Topic 6 Topic 5 Thursday, September 24, 2009

step 4, variation KEVIN Prior to passing, allow each participant to “save” one card that can’t be lost, and to discard one card that is the least important. ese cards should then be designated as “save” or “remove,” and then set aside from play. Topic 84 Topic Topic 7 Topic 1 Topic 5 Topic 23 Topic REMOVE Topic 6 SAVE Thursday, September 24, 2009

step 5 KEVIN Repeat steps 3 and 4 up to 3 times, with each participant prioritizing with their new set of cards, designating the 3 lowest priority, marking them with new or additional hash marks, and passing them to the le. Thursday, September 24, 2009

step 6 KEVIN Aer each participant puts the cards in order a ﬁnal time, have them number the cards and place their initials on each card. At this point, each card should have a single set of initials, a number that represents the participant’s priority, and between 0 and 4 has marks. Topic 7 Topic 5 Topic 6 Topic 8 Thursday, September 24, 2009

step 6 KEVIN Aer each participant puts the cards in order a ﬁnal time, have them number the cards and place their initials on each card. At this point, each card should have a single set of initials, a number that represents the participant’s priority, and between 0 and 4 has marks. 1 2 3 4 Topic 7 Topic 5 Topic 6 Topic 8 KH KH KH KH Thursday, September 24, 2009

KEVIN analysis Analysis of the collected data assesses the priorities of the combined group and variations in priorities between the two represented groups. Thursday, September 24, 2009

Topic Passes Average Client Avg. Happy Cog Avg. Variation Abstracts of Research Projects 2 1.38 1.88 0.83 1.05 Blogs or Articles Written by Doctors 3 1.46 1.86 1.33 0.53 Blogs or Newsletters Written by Clients 4 1 0.71 1.33 -0.62 Blogs or Newsletters Written by Leadership 8 0.54 0 1.33 -1.33 Corporate Volunteer Tracking Capabilities 15 0.23 0.42 0 0.42 Discussion Areas for Parents/Caregivers 5 0.77 0.14 1.5 -1.36 Donate to a Speciﬁc Program 8 1.31 1 1.67 -0.67 General Information About Low Vision 0 6.08 5.57 6.67 -1.1 Guidelines for Accessibility on the Web 6 0.07 0.14 0 0.14 How to Find Help Near You 1 5.23 5.42 5 0.42 Integrated Events Calendar 12 1 0.14 2 -1.86 Reviews of New Assistive Technology 2 3.38 4.71 1.83 2.88 Services Organized by Visual Condition 2 6 3.57 8.83 -5.26 Sign Up to be a Volunteer 0 1.53 1.28 1.83 -0.55 Vision Loss Simulations 0 2.31 3 0.33 2.67 Volunteer for a Speciﬁc Program 1 0.46 0 1 -1 Out of 10, n=13 Out of 10, n = 7 Out of 10, n = 6 Thursday, September 24, 2009

other kickoff activities Thursday, September 24, 2009

other kickoff activities Ice Destroyers Thursday, September 24, 2009

other kickoff activities Ice Destroyers Prototyping exercise (Zaki Warfel) Thursday, September 24, 2009

other kickoff activities Ice Destroyers Prototyping exercise (Zaki Warfel) UX Health Check (Labate & Govella) Thursday, September 24, 2009

other kickoff activities Ice Destroyers Prototyping exercise (Zaki Warfel) UX Health Check (Labate & Govella) Ask “What Have We Done at Sucks?” Thursday, September 24, 2009

other kickoff activities Ice Destroyers Prototyping exercise (Zaki Warfel) UX Health Check (Labate & Govella) Ask “What Have We Done at Sucks?” Establish a social relationship Thursday, September 24, 2009

CHRIS design IN WHICH WE MAKE THE PRETTY SMARTER & MAKE THE SMARTER PRETTIER Thursday, September 24, 2009

CHRIS So, what’s wrong with the “IA to Design” waterfall process? Thursday, September 24, 2009

CHRIS Discoery IA Design • Initial visual design Thursday, September 24, 2009

CHRIS benefits Everyone is informed Client understand functionality Frees up teammates Thursday, September 24, 2009

CHRIS drawbacks Heavy burdern Design = “Skinning” Where’s the collaboration? Clients ﬁnd IA documentation scary & confusing Thursday, September 24, 2009

CHRIS visual concepting (Initial design concepts) 3 - 5 “uick Hit” visual designs Solve speciﬁc problems Cross-team eﬀort Thursday, September 24, 2009

CHRIS visual concepting (Initial design concepts) Share responsibility Explore unique solutions Provide a target Cra a shared vision Thursday, September 24, 2009

CHRIS Task: Redesigning Carlisle’s wideplankﬂooring.com capitalizing on the unique Carlisle story & selling process Thursday, September 24, 2009

CHRIS Task: Redesigning the Mozilla website while keeping the content & structure intact Thursday, September 24, 2009

CHRIS So what does this process (basically) look like, then? Thursday, September 24, 2009

Discoery CHRIS • Brainstorming • Collaboration • Initial visual design IA Design Thursday, September 24, 2009

JENN MARK development IN WHICH WE PUT OUR $ WHERE OUR ) IS Thursday, September 24, 2009

JENN MARK hello! Mark Huot Lead Developer and avid Red Sox Fan, Boo! Jenn Lukas Lead Developer and avid Phillies Fan, Woo! Thursday, September 24, 2009

(confused development cat) Thursday, September 24, 2009

Waterfall IA Design Development Improved Waterfall IA Design Development Thursday, September 24, 2009

(getting answers) (confused cat) Thursday, September 24, 2009

(inventory ﬁle) Thursday, September 24, 2009

(screen shot of login form) Thursday, September 24, 2009

(screen shot of inventory with just “login” page showing) Thursday, September 24, 2009

(screen shot of login form) Thursday, September 24, 2009

(screen shot of login form with forgot password link) Thursday, September 24, 2009

(screen shot of inventory with just “login” page showing AND forgot your password) Thursday, September 24, 2009

(screen shot of login form with forgot password link) Thursday, September 24, 2009

(screen shot of the reset your password email form) Thursday, September 24, 2009

mark@markh.ut.com email is entered wrong= Thursday, September 24, 2009

mark@markhuot.com (error page on forgot your password) Thursday, September 24, 2009

(screen shot of password has been successfully reset page) Thursday, September 24, 2009

(screen shot of inventory with just “login” page showing AND forgot your password AND reset form AND reset conﬁrmation) Thursday, September 24, 2009

markhot •••••••• (screen shot of login page) Thursday, September 24, 2009

markhot (screen shot of login •••••••• page with an error) Thursday, September 24, 2009

(screen shot of inventory with just “login” page showing AND forgot your password AND reset form AND reset conﬁrmation AND error page) Thursday, September 24, 2009

markhuot •••••••• (screen shot of login page) Thursday, September 24, 2009

(screen shot of success login page) Thursday, September 24, 2009

(screen shot of inventory with full login items) Thursday, September 24, 2009

Poppycock! Thursday, September 24, 2009

(screen shot/movie of ajax login form—apple.com rip off, web2.0 rip) Thursday, September 24, 2009

“Uhh ohh” pages Thursday, September 24, 2009

404 Pages Thursday, September 24, 2009

(example 1 of forgotten pages with bland developer speak) Thursday, September 24, 2009

No Search Results Thursday, September 24, 2009

(separate screen shot of no search results) Thursday, September 24, 2009

(screen shot of full inventory ﬁle) Thursday, September 24, 2009

the BIG IDEA IN WHICH WE ASSEMBLE, & TAKE THE FORM OF A BUCKET OF WATER Thursday, September 24, 2009

the BIG IDEA Thursday, September 24, 2009

the BIG IDEA We choose and treat our clients like we choose and treat our friends. Thursday, September 24, 2009

the BIG IDEA We choose and treat our clients like we choose and treat our friends. We (attempt to) manage our projects with ﬂexibility. Thursday, September 24, 2009

the BIG IDEA We choose and treat our clients like we choose and treat our friends. We (attempt to) manage our projects with ﬂexibility. We start our projects with engagement, depth, & energy. Thursday, September 24, 2009

the BIG IDEA We choose and treat our clients like we choose and treat our friends. We (attempt to) manage our projects with ﬂexibility. We start our projects with engagement, depth, & energy. We sometimes lead with collaborative visual thinking. Thursday, September 24, 2009

the BIG IDEA We choose and treat our clients like we choose and treat our friends. We (attempt to) manage our projects with ﬂexibility. We start our projects with engagement, depth, & energy. We sometimes lead with collaborative visual thinking. We insure our ideas are fully considered and developed to provide a consistent experience. Thursday, September 24, 2009

thank you happycog.com @iamjolly uestions & comments? @dtderu @kevinmhoﬀman @ccashdollar @jennlukas @markhuot Thursday, September 24, 2009

Solving Business Problems for Our Clients, Each Step of the Way

1 comments

Notes on slide 1

18 Favorites