Getting Things Done From Idea to User Experience By Nearsoft Inc Claudio Cossio @ccossio
Getting Things DoneFrom Idea to User Experience
By Nearsoft IncClaudio Cossio@ccossio
Claudio Cossio - @ccossioNearsoft Inc (@nearsoft)Work at Nearsoft Labs (R&D)Building prototypes from idea to Alpha/BetaWorking with 200+ developers
10+ years building & marketing digital productsDoing growth/user acquisition when it was Spamming
Todays Focus* More information on the projectwww.planningwithcards.comWill be using a real use case example *Full disclosure - internal project from R&D LabsWorking with 3 personasWe will work with user stories
TopicsIntroductionIdeasGoals (expectations)DataBehaviour SegmentationUX Roadmap
: B
IntroductionDifferences with Strategy & Planning
Strategy vs PlanningStrategy is an intent not a planStrategy is a set of hypothesesWith strategy you build a rationale for UXPlanning focuses on business outcomesPlanning is tactical and focuses on execution
Strategy is focused on CAUSE & effect on how to achieve our business goals.
Planning grabs those hypotheses and decides which ones to execute based on the best possible outcome for our business.
Create a strategy & plan with dataProduct Owners need data to make a planSources are Analytics, Sales, CRM & market reportsYou need to get all stakeholders involvedUser Research minimizes the risk of an undesirable product
Business & Users/clientsData outcome for each personaBenchmarking data on competitors is essentialYou need to know what its out there and position your offerAligned to the current Product roadmap
????
Example:
Example - PlanningWith.CardsEstimate software development effortImprove accuracy of those estimatesRemote developers & product owner/scrum masterBased on Planning Poker techniqueCommunication through chat platforms
IdeasA product is hired to perform a job
IdeasMany possible scenarios, but only 1 outcomeOutcomes focused on user/business goalsMaintain a balanceFocus on the client/user intent
Why are we doing this?
Example - PlanningWith.CardsOutcome: Numeric estimation of each taskData: Fibonacci, Days & Hours cardsUser: Developer, Onlooker & Scrum MasterEnvironment: Web - Hangouts/HipChat
What is your product? In order to _______________________ (Vision),our product will solve ______________ (Target Audience)problem of ______________________ (User Problem)by giving them ___________________ (Strategy).We will know if our products works, when we see _______ (Goal)@JAF_Designer
Goals
UX has 2 main goals to align - Biz & User
Poner un slide para hablar de los stakeholders, sobre todo del developer es importante que este lo mas cerca posible para que pueda ver que es viable implementar
Que est expuesto directamente al problema, ellos son la fuente primaria y ms realista de lo que se puede construir
Business & User goalsUserNeeds something from your app or websiteBusinessHow a product generates profits from its use
Credit to Nikkel Blaase
Nikkel Blaase via Medium
Amazon1 Click CheckoutYoutube & GoogleEarl Wilkerson via Flickr
Goals - PlanningWith.CardsDeveloperEstimate privately & as accurate as possibleOnlooker (stakeholder)Provide feedback on tasks being estimatedScrum MasterManage a backlog of the rounds & estimations
Goals - PlanningWith.CardsBusinessMake it easy for teams to estimateConnect to PM toolsOffer a backlog service ($)
$
Import stories fromJIRA/Trello/PTrackerPrivateVotingVirtual Cards Hangouts/HipChatShow & SaveResultsJohn Ivara via Flickr
DataTraces that the people who use technology leave behind
ResearchList potential actions for your productCard sorting of those actionsUser JourneysBenchmarking the competition
What they want||DesireAbbyladybug via Flickr
Insights into Navigation
Expectations
Align with stakeholders
CARD SORTING.Insights into expectations about navigation
Sort out whats important, what isnt, and where it all goes.
decide whats really important for the users.
What they will do
Interactions
Goals, needs & expectationssea turtle via Flickr
USER JOURNEY.
Many of us focus on how users will do something.
Determine the interactions neededBuild from a customers point of view, not an internal business point of view
Strengths
Weakness
Unattended needsPhilip McMaster via Flickr
UX & DataProving a pointImproving an experienceDiscover something new (not obvious)
Actions - PlanningWith.CardsCoordinate call/chat on Hangouts/HipChatCreate/Import Tasks/StoriesConfigure cards to use for estimatingChoose a card for estimating a taskWatch an estimation roundRepeat a round
User Journeys - PlanningWith.CardsDeveloperScrum MasterStakeholder (Onlooker)
User Journeys - PlanningWith.Cards
Estimate
CoordinateDecideAgree
Select TasksScrum Master
AttendDeveloper & OnlookerOnlooker
ManageRoundScrum Master
Feedback
Pick CardDeveloper
RepeatRound
Save DataScrum Master
New Round
Competition - PlanningWith.CardsUnattended needsIntegrate into a communication platformDifficulty for Onlookers to participateLack of data after the estimation process
Identifying patterns Behaviour Segmentation
Roles & Traits
Identifying who will be using your product (roles)Traits (attitude, demographic, goals, etc)Trait spectrum
Kristin and Adam via FlickrContext
Environment
Rewards
Trait spectrumCategoryContext VariablesType of RoleIdentity, Demographics, Intent/Goal, Cognitive AbilityTimeTime of the Day, Day Parts, Day of Week, Weekday/Weekend, HolidaysLocationHome, Workplace, Commuting, Stores, Restaurants/Cafes, Recreational AreasInteractionsChannel (Mobile/Web), Medium (Text,Video, Audio), DevicePhysicalEnvironment & surroundingsActivityAny number of user activities the user is involved
* Knowledge@Wharton - University of Pennsylvania
Roles - PlanningWith.CardsCategoryContext VariablesScrum MasterGoal: Manage estimate according to deadline & moderate the rounds | Demographic: Male/Female | Mood: Patient & observing TimeWorks: Weekdays and Saturday.Scrum Activities: Tuesday to Thursday.LocationWorks from: Home, Office, CoWorking & events.InteractionsChannel: Web & Apps | Device: Laptop & Mobile | Medium: Chat Platforms & Project Management ToolsPhysicalMostly quiet spaces & occasional noisy places.ActivityMulti tasking chats & video calls. Taking notes and writing minutes. Project management tasks. Group Meetings: Daily's & Standups.
Roles - PlanningWith.CardsCategoryContext VariablesDeveloperGoal: Estimate tasks accurately | Demographic: Male/Female | Mood: Hesitant, Distracted, Nervous, Uneasy & PatientTimeWorks: Weekdays and Weekends | Daily Standups Code Review: Tuesday to Thursday.LocationWorks from: Home, Office, Coworking spaces & cafes.InteractionsChannel: Web & Apps | Device: Laptop & Mobile | Medium: Chat/Video Platforms & Code Review ToolsPhysicalMostly quiet spaces & occasional noisy places.ActivityMulti tasking chats & video calls. Coding. Code Review meetings. Group Meetings: standups & assessments.
Roles - PlanningWith.CardsCategoryContext VariablesOnlookerGoal: Provide Feedback for better estimations | Demographic: Male/Female | Mood: Analytical, Patient & Observing.TimeWorks: Weekdays and Saturday | LocationWorks from: Office & Coworking spaces.InteractionsChannel: Web & Apps | Device: Laptop & Mobile | Medium: Chat/Video Platforms PhysicalMostly quiet spaces & occasional noisy places.ActivityMulti tasking chats & video calls. Group Meetings: Business, Marketing & Product.
Patterns - PlanningWith.Cards
MultitaskingChat/Video platformsRemote Locations
Patterns - PlanningWith.Cards
UX Roadmap
Building consensus across the board
Poner un slide para hablar de los stakeholders, sobre todo del developer es importante que este lo mas cerca posible para que pueda ver que es viable implementar
Que est expuesto directamente al problema, ellos son la fuente primaria y ms realista de lo que se puede construir
Users
Where they are.Where they want to be.How our product will help them along the way.
A....Z
Business
Capture & present insights.Complex interactions.Aligned with Stakeholders.
Show the whole team what you discovered.What occurs across experiences with a product, service, or ecosystem
What can & cannot be done.Relationship with product/users.Fresh insights.
Stakeholders
The Developers point of view is crucial for tech related projectsWhat occurs across experiences with a product, service, or ecosystem
Invalidate your assumptions.Live mockups.Save development time.Reality Check
Dont look for validation, since the product will change.It is important to test how your product will behave.At the end of the day you need to have a goal in testing your assumptions.
Example - PlanningWith.Cards How we used Experience Design to test our mockups
Example - PlanningWith.Cards
QuestionsTo continue the conversation, please tweet your comments & questions to @ccossio with #MakeIt
Thank you!Claudio Cossio
By Nearsoft [email protected] @ccossio