THE SERVICE BLUE PRINT OR FLOW CHART
• • •
A diagram of a user’s path through an experience, including physical, in person, and screen
touch-points. They are large diagrams that can easily communicate a complex flow (especially if there are multiple interactions with multiple personas, spread over several days, weeks, months)
Think: modeling the life-cylce of a facebook message (notifications, emails, shares, likes, comments..)
IT COMBINES A CUSTOMER JOURNEY MAP WITH A FLOW CHART (UML) MODEL
You can model the current state during discovery phase (model the problem)
and the beginning of the future state (model the solution)
We're going to do the future state.
Done after concepts, when you want to dive deep into the work-flow
The VISUAL diagram is useful in communicating the complex interactions of any scenario for yourself team, clients, and stakeholders can understand.
Service Blueprints are great for diagramming a work-flow that:
1. Spans multiple mediums of interaction that are not just software
(Email → website → ordering → delivering → in-person interaction → reviews)
2. Great at showing how a system/experience works for multiple personas
3. Processes that can spans hours, days, weeks, or months
4. Modeling experiences that use IOT devices and connect to application workflows
WHY THIS TOOL IS VERY HELPFUL?
IF YOU"RE TRYING TO FIGURE EVERYTHING OUT FROM A SCREEN TO SCREEN TYPE WORK-FLOW — IT CAN BE CHALLENGING, TIME CONSUMING AND YOUR RISK SPENDING TO MUCH TIME ON LAYOUT BEFORE UNDERSTANDING THE ENTIRE SYSTEM OR WORK-FLOW FROM END-TO-END.
THIS TOOL WILL FORCE YOU TO FIGURE OUT THE WORK-FLOW FROM A MODELING PERSPECTIVE —MEANING YOU WILL FIGURE OUT THE WORK-FLOW WITHOUT THE NEED OF LAYOUTS, PHOTOS, BUTTONS, TRANSITIONS & DESIGN ELEMENTS.
BECAUSE YOU HAVE TO FIGURE OUT ALL THE CONTENT YOU WILL NEED FROM START-TO-END — IT WILL HELP EXPOSE THE AREAS YOU DON'T KNOW AND THIS IS WHERE YOU CAN ASK FOR HELP FROM OTHER TEAMMATES, STAKEHOLDERS OR SUBJECT MATTER EXPERTS
THIS TOOL ALSO ALLOWS YOU TO CREATE WITH OTHER NON DESIGNERS, —YOU AND THE PM CAN CREATE THIS TOGETHER. YOU CAN WHITE BOARD IT TOGETHER AND THE DIGITIZE THE WHITE-BOARDING AFTERWARDS.
YOU CAN ALSO SHARE THIS WITH ENGINEERS AND GET FEEDBACK ON THE SYSTEM BEFORE YOU EVEN START DESIGNING SCREENS AND HERE'S THE KICKER....ENGINEERS CAN START WORKING WITH JUST THE MODEL. THEY CAN START WITH BASIC HTML (TEXT AND BUTTONS) BUILD OUT THE DATA BASES, LOOK INTO SERVICES LIKE PAYMENT (STRIPE), DOC SIGNING (DOCU-SIGN) ETC.....AND THEN THEY CAN STYLE THE SCREENS LATER WITH CSS ONCE YOU HAVE DESIGNS READY.
MOST IMPORTANTLY, DURING A DESIGN INTERVIEW
THIS IS THE #1 ONE TOOL WE LOOK FOR WHEN DOING A ON-SITE DESIGN WHITE BOARD CHALLENGE. WE WOULD PROMPT A TWO PERSON INTERACTION AND SEE IF THE DESIGN INTERVIEWEE COULD MODEL A WORK-FLOW THAT HAS A 2+ PERSON INTERACTION WITH NOTIFICATION (TOUCH-POINTS).
FEATURES BUT IN STORY FORMAT -
ONE FEATURE CAN HAVE MANY SCENARIOS TO DESIGN FOR
BREAK YOUR APP
ITS WAY EASIER TO MANAGE & DESIGN THE WORK-FLOWS
EX: SCHEDULING A
YOU ONLY NEED TO MODEL
YOUR MAIN HAPPY PATH SCENARIO
YOU CAN DO MORE IF LIKE....EXTRA GOODNESS
BY GOING FIGMA
HERE IS THE PRINCIPLES OF UML