UX | Creating the User Journey

Creating the User Journey – map of screens as core UX design practice
itCraft Services | Sep 12, 2019

Customer Journey Mapping – the road to be taken within the app to do what you want to do, requires a proper map. The better the map, the more enjoyable the Journey.

What is a screen map?
A screen map is a diagram showing individual application screens, their location (hierarchy) and interrelationships

Why make screen maps? The map allows you to visualize how many screens the app will have and show the relations between them. It is invaluable in estimating the workload for the UX / UI design process.

Turning user stories into a user journey map = Individual “User stories” are sorted into groups to be included in specific screens of the application. Next, the screens are marked on the map to reflect the hierarchy between them and to visualize actions (transitions) performed by the user.

Examples of screen maps

What is User Flow used for?
User flow is a diagram showing the path(s) a User can take in the application
. It visualizes the decision making moments and presents all use-case scenarios. The User Flow is helpful in analyzing the ways Users reach their intended destinations or achieve particular goals.

User Flow role
Designing User Flows allows us to adjust and perfect the operation of the app and avoid flaws in interaction between Users and the software.We are able to identify the “Pain points” of the system and improve the process well ahead of development.

What is a low fidelity wireframe diagram?
Low-fi (low fidelity) Wireframes are a simplified view of the structure of the application screens
. The screens are usually presented in grayscale and without details.

Instead of a detailed design, our goal here is to plan appropriate distribution of key UI elements, and their hierarchy. The screens propositions should be easy to draw, edit and copied. Low-fi wireframes creation should be a quick process of establishing a base for team discussion, adjustments and clarification of requirements.

They can be prepared on a piece of paper or in a dedicated program such as: Sketch, Proto.io, UXPin, Axure, Balsamiq. The choice of tools is up to you.

What is a high fidelity wireframe?
High fidelity wireframes expand the low-fi version by refined, platform specific UI elements (iOS, Android, Windows), content and graphics reflecting future appearance of the application

What is the difference between high fidelity and low fidelity wireframes?
The main difference between these two wireframes is the level of detail.

The low-fi wireframes focus on the general appearance of the main functionalities, without detailing of particular elements, content or pictures, using placeholders instead.

Low-fidelity wireframes are not a reflection of the final look of the app. They present the general idea and vision of the application, and need to be made as quickly as possible. They help in discussions with the team and the client in the conceptual process, when determining the scope of work required.

In high-fidelity wireframes, we refine the low-fi screens. Hi-fi is more labor-intensive, as we need a higher level of detail – shapes, content, UI elements, the screen composition and relations between them all must now closely reflect the final look of the app.

High-fidelity wireframes are a more sophisticated representation of what the application’s final look.

Why use the UI Kit in the UX / UI design process
When designing an application interface – the UI for either Android or iOS, you should always keep in mind the differences in appearance between platforms. Some elements of iOS, Android UI differ significantly in both looks and the way they work. Buttons, date pickers, text fields, notifications are all designed differently. The makers of mobile systems – Apple and Google provide complete design guidelines on their websites, as well as ready-to-download components.
To simplify the design process and save time, we don’t usually create new elements from scratch. Designers often use ready-made UI kits and libraries. They contain ready-made elements that can be imported into projects and customized according to needs. Depending on whether you are designing a low or hi-fi wireframe, a variety of UI Kits are available for both iOS or Android platforms.

Establishing a good base for the UI/UX design benefits your mobile app development in many ways:

The customer saves time and resources (quick way to verify the product concept),
A small number of specialists needed to start the process, which translates into lower costs,
The client takes active part in the design and provides invaluable input on the functionality and appearance of the application,
The client can verify that the application design is according to requirements and best practices,
Faster application development time – the team will have a clear picture of how the application is supposed to work and look,
Ability to test the application early in the production process. A clickable prototype lets you experience the operational functionalities of the app before programming starts,
Flexibility of the design process – changes and adjustments can be done quickly and without the need of engaging developers work.

Author = Piotr Niedźwiecki (itCraft Services)

URL = https://itcraftapps.com/blog/user-journey-map-of-screens/

Tool | BuildFire (Mobile App Dev)

Mobile App Development Timeline: A Realistic Perspective
buildfire | undated

Note = The Most Powerful App Maker For iOS & Android
BuildFire’s powerful and easy to use mobile app builder makes it so you can create mobile apps for iOS & Android in a fraction of the time and cost.
Simple and intuitive app builder – No coding required
Build custom functionality with our developer SDK
Build for FREE for 14 days. No credit card required
URL = https://buildfire.com/

Author = Ian Blair (build fire)

URL = https://buildfire.com/mobile-app-development-timeline/

Mobile Apps | Onboarding, w/Examples

The 10 best user onboarding examples to learn from
Appcues | Undated (2019? 2020?)

Top 10 favorite user onboarding examples:

Slack: Educates users with empty states and a friendly bot
Duolingo: Leads with the product experience
Grammarly: Takes a “learn by doing” approach
Tumblr: Charms with personality and personalization
IBM’s Cognos Analytics: Delivers consumer-grade UX in an enterprise product
Avast: Gives value before you ask for buy-in
Toggle: Lets users learn at their own speed
Avo: Makes signup easy and worry-free
TikTok: Teaches users how to get even more value from the product
Reclaim: Introduces users to your way of thinking

The basics of great user onboarding
Onboarding is the process of acquainting a new user with a product
. A great user onboarding experience shortens your new users’ time to value, guides them to their aha moment, and gets them to activate faster.

8 great user onboarding UX and UI patterns
Throughout our extensive research into what makes for amazing onboarding, we’ve found that there are 8 onboarding UX and UI designs that commonly contribute to a better onboarding experience. These include:
A welcome message greets the user with a short, friendly message that acquaints them with the product.
Product tours explain the product features most important to each user.
Progress bars indicate how long the onboarding experience takes, so users know how long they’ll need to commit.
Checklists provide an explicit list of tasks for the user to complete.
Hotspots direct attention to certain product features without interrupting their workflow.
Action-driven tooltips are small pop-ups that provide advice when a user performs a specific action.
Deferred account creation drops the user right into the product without requiring the user to register.
Persona-based onboarding tailors the product experience based on the user’s responses to a short survey.

These onboarding experiences are not mutually exclusive—many products will include 2 or 3 of these patterns depending on what their users need. Consider these a toolbox of sorts. When designing your onboarding, see how you can introduce these 8 UX and UI patterns to improve the user experience. If some of them don’t have a place in your onboarding flow—don’t sweat it.

All onboarding experiences should follow 4 steps
These 4 steps of successful user onboarding are:
Drive users toward key actions: Understand what actions are most likely to drive activation in your product and then build your onboarding toward getting users to those points. For example, if data shows that users who sync their Google calendar with your product are more likely to renew after the first month, then prioritize syncing users’ calendars in onboarding.
Focus your product around onboarding first: Just because your onboarding has a goal in mind doesn’t mean it can skip everything else. Make sure you show users everything they need to know before you get to your key action.
Add new UI where it’s needed most: Find areas that might be confusing or difficult for new users and use UI patterns to make it easier. Maybe that’s a modal that describes a feature, a tooltip that explains a button’s function, or a hotspot that draws the eye of a user.
Analyze, adjust, and repeat: No onboarding experience is perfect, and even the best onboarding experiences continue to be experimented on and updated. Conduct user research and run A/B tests to find out how you can make your onboarding even more effective at improving product adoption.

10 onboarding examples are commented

Onboarding FAQs

What is user onboarding?
User onboarding is the process of educating users and showing them the value of your product.
The onboarding process starts the first time someone tries your product and ends when they either churn or become a regular user. For some products, this means onboarding will be a matter of minutes, while others might require days to get people to a point where they can comfortably use the product as intended.
The primary goal of onboarding is to teach users about your product, personalize the product for their needs, and lead them to their aha moment—the first time they see the benefits your product can bring.

Why is user onboarding important?
User onboarding is important because it helps ease users into a new product. It’s a chance for them to be shown how it works, so they don’t have to waste time figuring it out on their own.
User onboarding is also crucial for companies. A good introduction of your product improves the overall user experience as users are introduced to product features and how to use them. When the onboarding is successful, it directly impacts customer retention, one of the most important profit metrics. If you improve retention by only 15% in the first week, that could boost revenue by 40% as each succeeding week’s cohort staves off churn that much longer. Great onboarding is how you achieve this.

How do you design a good onboarding experience?
A good onboarding experience is created when:
New users are given the tools and knowledge to be successful.
The onboarding experience is purposefully designed to guide users toward a key action that promotes activation.
Onboarding experiences are personalized based on segmentation.
UX and UI design is informed by user feedback and data to create an easy and intuitive process.
You invest in tools that make it easier to give users the experience they’ve come to expect.

If you do all 5 of these things well, then your onboarding is on the way to improving overall product adoption and reducing churn.

Author = Jackson Noel (Appcues)

URL = https://www.appcues.com/blog/the-5-best-user-onboarding-experiences

Planning | Product Roadmap

What is a Product Roadmap? And How to Create One
Product Manager HQ | Dec 22, 2021

The purpose of a product roadmap is to identify key steps to take and when to take them.
Crafting a product roadmap is no different from planning a road trip. Think about the last trip you planned. You likely first began by identifying key destinations, key dates, and a theme of what kinds of experiences you wanted to get from your road trip.

What is a Product Roadmap?
A product roadmap is a guide that describes the steps you need to take in order to reach your product goals. It’s a plan of action that lines up a product’s short-term and long-term goals. It also outlines how you hope to achieve those product goals.
Product roadmaps can span a variety of timeframes. That’s because different companies and teams can have different timelines.

Types of Product Roadmaps

  1. The Evolutionary Roadmap = This roadmap is a great tool for keeping everyone in sync when there isn’t a lot of information about how the final product will look. This type of roadmap is a solid choice to keep developers, designers, and project managers in sync.
  2. The Release Roadmap = This is the product or marketing team’s most important tool to communicate with the customer community about what features are going to be released and when. Product managers create release roadmaps once the product team has accomplished significant work on all major features planned for the release.
  3. The Theme Roadmap = This roadmap is a logical way to communicate the next features that will be implemented in an effort to meet company goals or customer needs. This map indicates where the product is going and how it plans to get there.
  4. The Timeboxed Roadmap = This is similar to the release roadmap but has more specifics about certain features or types of releases. Similar to a release roadmap, this map is detailed. However, it does not include dates. It serves as a reminder and communication for the team that work should be completed in time for a certain date.
  5. The Capacity Roadmap = This one is similar to the release roadmap but without dates. Capacity roadmaps serve as communication tools among departments or functions and show the types of products that the team will create. Product managers tend to use this product roadmap to discuss resources needed as opposed to specific deliverables.
  6. The Market Requirements Roadmap = This roadmap helps a company steer its product and market positioning. It also shows how the plan and types of products match requirements from the customer or user base.
  7. The Opportunity Roadmap = This one is used for companies that sell to businesses. It helps align business development efforts with strategic initiatives so that customers can be acquired in a coordinated way. For example, product managers create this type of roadmap once a significant amount of work has been completed on all major features planned for the release.
  8. The Project Roadmap = Product leaders use this roadmap to align teams and individuals working on different products or projects with each other. It lets people see how their work fits in with the rest of the company’s plans for that release.

How to Build a Product Roadmap
The first step in building a product roadmap is defining the product strategy. That comes from the vision you have for the product. Then, you and your team will need to gather information from two main sources. Those are your customer support or sales team and your product users.
This will give you a good base for assigning a timeframe to your initiatives.
Keep in mind that a product roadmap should be a strong foundation for all decisions, but it should be flexible. After all, the landscape might change and you might need to re-prioritize.

Why is a Product Roadmap Important?
A powerful product roadmap is built to serve a product strategy.
In product management, you’re faced with multiple viable alternatives all of the time. A product strategy mandates that you select one viable alternative out of many and that you say ‘no’ to many other alternatives.
Because a roadmap forces you to take your journey one step at a time, it means that you will take a specific step in a specific sequence. This helps the team to have a structured plan to follow.

Product Roadmaps Serve a Larger Purpose
They’re also powerful tools for aligning internal stakeholders with the direction that your product is headed. As an example, providing sales teams with visibility on where your product is headed will enable them to sell more confidently in the field. Doing so allows you to secure the buy-in of executives from various internal departments.

Product Roadmap Template
One simple way to structure your product roadmap is to ensure that each row includes the following columns:
New product feature idea
User story and requirements
Effort required = You’ll have to work with your team to figure out the best way to define the effort required. This could be a time or $ cost
Sequence = Which items should be done first? Which items should be done later? Be sure to use prioritization to identify what will give you the strongest ROI, or return on investment.
Estimated release date = Remember to keep this high-level and either come up with or work with your engineering manager to estimate the time required to complete the feature

Best Product Roadmap Tools
While product managers tend to be tool-agnostic, you can get ahead of the curve by familiarizing yourself with these popular roadmapping tools.
ProdPad: Lets you capture ideas and feedback, create product specs, and build a product roadmap.
ProductPlan: Lets you plan and communicate your product roadmap.
ProductBoard: System of record for product management that helps teams make products people want.
Aha!: Web-based product strategy and roadmapping software for agile product managers.
Roadmunk: Visual roadmap software for product management.
Jira: A flexible and scalable issue tracker for software teams.
Excel: A straightforward way to put together your thoughts.
Google Sheets: Easy for startups to use to quickly collaborate on feature ideas.

Author = Clement Kao

URL = https://productmanagerhq.com/what-is-a-product-roadmap/

Roles | Project Manager vs Scrum Master vs Product Owner

Project Manager vs Scrum Master vs Project Owner
Visual Paradigm | Undated

Role of Project Manager
The traditional Project Manager is a leader, a decision maker, a planner who manages the project and his team and is the person accountable to the business for accomplishing the project objectives. Project manager’s role is to manage the projects and ensure that the project meets the requirements.

The roles and responsibilities of the Project Manager includes:
Define project scope
Gather requirements
Identify activities, dependencies, sequencing, and time estimates.
Identify resources needed
Manages the budget
Reports to business leadership on project progress
Focuses on process
Allocates tasks
Prioritizes features
Ensure quality
Manage vendors
Manages risk

Role of Scrum Master
The Scrum Master doesn’t manage the team that produces the work, instead he supports the Product Owner, coaches the team and makes sure that Scrum processes are adhered to. The Scrum Master is responsible for the Scrum process, its correct implementation, and the maximization of its benefits.

The role of the Scrum Master is more a coaching and facilitation role, a role that sits between the project and the customer and the role includes:
Lead Sprint Planning
Lead / Organize the daily Scrum Meeting
Coaches the product owner
Monitoring the progress of the sprint
Helps team estimate and increase velocity
Promotes continuous communication
Reduce team disruptions
Monitors and helps improve team dynamics
Assist with Reporting
Motivates the team
Acts as the glue that holds the team together

Role of Product Owner
Product Owners have a huge responsibility for the project. They are responsible for maintaining a product backlog that describes the product that must continue to fit with the requirements of the business. During any project, as more becomes known about a product, about customers, or about changes in the market, a product often needs to change in order to meet these requirements. The Product Owner has to adjust and re-prioritise the backlog to fit these changes and to steer the project.

Project Owner’s role includes:
Convey a clear vision of the project
Manage and prioritize product backlog
Ensure development team understand tasks and work on the right features in the prioritized order
Provide feedback and sign off work results

Difference between Project Manager and Scrum Master
In Waterfall, the Project Manager takes a leadership role in leading the team and developing and managing the plan. But what about all those project management activities if the team is Agile?
A project manager helps manage the project timeline, resources, and scope in order to meet business requirements. A Scrum Master, however, helps ensure the scrum team is successful.
A Product Owner works with the customer and team to set direction.
A Scrum Master is a coach and facilitator and coaches the development team in executing Agile practices to complete the work the Product Owner prioritizes.
The Scrum Master works with the Product Owner and the development team to ensure the team members can move forward with development with no impediments, and that the Scrum practices are carried out.

Note That: There is a time or place for a project manager in the large projects. The Project manager can cover multiple teams and can work with other dependent teams as well. Project manager can coordinate with multiple teams, help them to meet project timelines and collaborate when resources are required.

URL = https://www.visual-paradigm.com/scrum/project-manager-vs-scrum-master-vs-project-owner/

Mobile Apps | Case Studies (Peerbits)

peerbits App Case Studies
peerbits | Undated

Real-time tracking app, real-time tracking and remote diagnostics
URL = https://www.peerbits.com/case-studies/real-time-tracking-solution.html

Social networking iOS app, connect with new people
URL = https://www.peerbits.com/case-studies/social-networking-app-for-iphone.html

Petrol filling station app, the official app for the largest chain of filling stations in Oman
URL = https://www.peerbits.com/case-studies/petrol-filling-station-management-app.html

ATM food solution, an IoT-controlled automated marketplace
URL = https://www.peerbits.com/case-studies/atm-food-solution.html

Marketplace app, GetItDone
URL = https://www.peerbits.com/case-studies/getitdone.html

URL = https://www.peerbits.com/case-studies/m2r.html

Fishency, building a better way to fish like a pro
URL = https://www.peerbits.com/case-studies/fishency.html

URL = https://www.peerbits.com/case-studies/jewlot.html

Nurse Alert, a cohesive solution to nursing activity
URL = ttps://www.peerbits.com/case-studies/nurse-alert.html

Apply, a tinder-like job search app
URL = https://www.peerbits.com/case-studies/apply.html

Photograff, Graffiti
URL = https://www.peerbits.com/case-studies/photograff.html

URL = https://www.peerbits.com/case-studies/repd.html

Epic Delivery
URL= https://www.peerbits.com/case-studies/epic-delivery.html

Throne, the eCommerce Marketplace App
URL = https://www.peerbits.com/case-studies/throne.html

URL = https://www.peerbits.com/case-studies/seatsplanet-travel-app.html

BusMaps, plan bus trip with navigation travel app
URL = https://www.peerbits.com/case-studies/busmaps-navigation-app.html

URL = https://www.peerbits.com/case-studies/tapnsell.html

Loyal Books

Frimb, Food & Drink app that connects socially and share recipes globally with food lovers
URL = https://www.peerbits.com/case-studies/frimb-food-drink-app.html

Fashion Sizzle, capture and share the clothing trends with fashion lovers on FashionSizzle. success story
URL = https://www.peerbits.com/case-studies/fashion-sizzle-photo-app.html

Peerbits Works
URL = https://www.peerbits.com/works.html

Author = peerbits

URL = https://www.peerbits.com/case-studies.html

Roles | 10 Steps to Becoming a Great Agile Coach

The 10 Steps to Becoming a Great Agile Coach | 58 minutes
LeadingAgile | April 2020 (TriAgile 2020)

The 10 Steps to Becoming a Great Agile Coach | 58 minutes

In this remote talk from TriAgile 2020, LeadingAgile CEO Mike Cottmeyer uncovers the 10 steps you can take to become the great Agile coach you always wanted to be, along with the four primary skill areas that make a great coach and the hard skills you’ll need to develop to get there.

Primary Skill Areas That Make a Great Coach
#1 Developing Hard Skills
#2 Getting The Right Experiences
#3 Fitting In To Your Company Culture
#4 Being A Good Community Citizen
#5 Recognizing Your Belief System
#6 Understanding Your Default Behaviors
#7 Developing Emotional Intelligence
#8 Learning To Think Fast On Your Feet
#9 Working Through Solutions
#10 Pattern Recognition, Systems Thinking, and Planning
Coaching Roles at LeadingAgile

Author = Mike Cottmeyer

URL = https://www.youtube.com/watch?v=sXgLMmpe7yI

Milestone | RIP Sally Ann Howes (1930-2021)

Sally Ann Howes death: Chitty Chitty Bang Bang’s Truly Scrumptious actor dies aged 91
Independent | Dec 22, 2021

Chitty Chitty Bang Bang actor Sally Ann Howes has died, aged 91.

The star, who played Truly Scrumptious in the 1968 musical film alongside Dick Van Dyke, died on Sunday 19 December, according to The Times. No cause of death has been disclosed.

Sally Ann Howes as ‘Truly Scrumptious’, in ‘Chitty Chitty Bang Bang’ (photo credits = Moviestore/Shutterstock)

Author = Ellie Harrison

URL = https://www.independent.co.uk/arts-entertainment/films/news/sally-ann-howes-chitty-chitty-bang-bang-death-cause-b1980580.html

URL = https://en.wikipedia.org/wiki/Truly_Scrumptious