Articles

10 Key Principles of User-Centered Design

,

Many firms’ design and development decisions are increasingly oriented toward human-centered innovation. Instead of rushing goods to market, these firms are using a user-centered design approach.

Design and development teams build high-performing digital products or websites that uniquely meet customers’ demands by concentrating on the user experience. After all, a good web design is helpful in boosting the business reputation or user experience.

This post will define user-centered design, discuss its fundamental principles, and describe the user-centered design process.

What Is User-Centered Design?

To create an enjoyable solution to a problem, user-centered design is a collection of iterative design processes concentrating on the user’s needs at each step. In UCD, the expectations, objectives, and preferences of the user significantly impact design decisions.

Additionally, users are actively involved in the entire process from start to finish. User-centered design principles encourage designers to create products with users rather than just for them. This strategy typically includes user research, interviews, usability testing, and a massive amount of feedback gathering.

UCD Requires Four Fundamental Components:

  • Visibility: Can people see what your website is about and how to utilize it the moment they land on your page?
  • Availability: Is your website user-friendly? Can they swiftly locate information? They should be able to find call-to-action buttons, menus, filters, and search choices with ease.
  • Legibility: Is the text simple to read for users?
  • Language: Is the language simple to grasp for users? Do you avoid using industry jargon in your UX authoring, which might lead to confusion and hesitation?

What Is The Significance Of UCD?

User experience is important in product design, especially in digital products such as app design, web and interface design, and marketing. Customers want their lives to be simplified. A website, app, or product exists to fulfill a consumer. Hence its success is determined by their interaction with it.

The following are some of the advantages of a user-centered design strategy for a business:

  • Customers keep coming back for more
  • There would be an increase in sales
  • Creating polished, efficient, and widely available goods
  • Understanding challenges thoroughly to provide suitable solutions
  • Customers and teams working together
  • Avoiding typical blunders
  • Enhancing Competitiveness
  • Assisting them in comprehending their market

It offers consumers the following advantages:

  • Making their life easier
  • Fulfilling their desires
  • Companies making them feel heard and understood
  • Making them feel important in the creation of things they use
  • Providing answers to challenges they were unaware they had or could not imagine solutions to

Let’s dig in to learn more about the advantages of UCD.

Businesses can benefit from using the user-centered design approach in various ways. As you incorporate this into your web development, you can enjoy the following four main advantages.

1. Prevent Project Failure

Your company might find it simpler to incorporate improvements and ensure your product is in line with actual user needs if you have a continuous feedback process assessing how customers react to your product, like a website.

Customers feel like their needs are better represented in the finished product, which can increase engagement and strengthen the bond with the company.

2. Improve ROI

This method produces products that more accurately reflect user expectations. The procedure also lessens mistakes made by website users, for instance. When combined, these factors motivate users to convert from leads to paying clients, boosting return on investment.

3. Increase Development Efficiency

In user-centered design, the objectives of the various team members are aligned. This can help clarify the best course of action for all parties involved. A more targeted, goal-oriented development process may be encouraged by the regular evaluation process.

Additionally, businesses can engage stakeholders and explain how their efforts and methodologies will improve customer interactions by using an iterative life cycle during product development.

4. Up The Level Of Competition

Customers will more fully appreciate what you offer, improve their engagement with your product or website, and be more likely to purchase from you if your product is created with their needs and expectations in mind.

As a result, this may increase your ability to compete in your sector.

5. KPIs Are Included

Given your user needs and business objectives, how do you move from the first to the second? You can measure key performance indicators with this in mind once you know what user needs are essential for the overall goals.

For instance, productivity may be the focus of office software, shopper activity may be the focus of sales tools, and retention rates may be the focus of other apps. All of these are necessary steps toward achieving business values like profit and revenue.

Human-Centered Design Versus User-Centered Design

There is a significant difference between humans and users. Simply put, all users are humans; however, not all humans will use your product. Therefore, you must thoroughly understand your target market to produce a successful user-centered design.

Detailed research should be done on the problems and goals of your users. Then, talk to them and give them several chances to offer feedback. By doing this, you’ll create a user persona that is complete and that you can use to determine the priorities for your design.

It’s critical to understand that different user groups may have additional requirements, levels of technical expertise, and expectations for using products like the one you’ve made.

What crucial guidelines or principles should designers consider when adopting a user-centric design?

The Process Of User-Centered Design

Certain fundamental principles underpin user-centered design. While the development process is always iterative, no explicit methods for implementation are specified. The approach can be implemented in either a waterfall or an agile environment.

1. Contextualization

The first step is to analyze the environment in which users will use the product. What are the intended applications of the product for future users? Teams working on projects can get answers by watching and talking to potential users.

2. Outlining The Prerequisites

Specifying the requirements for the new product is the second step. In this step, user requirements are described while considering corporate needs.

3. Design

Once the requirements are established, the actual design process can begin. Designers typically start by producing a straightforward prototype, like one made of paper, then move on to digital wireframes and a finished prototype.

4. Analysis

The project team solicits feedback from potential users after creating a prototype. This is typically done for digital applications through in-depth user testing and qualitative research.

Do surveys and tests evaluate user satisfaction, effectiveness, and efficiency? With the new information, the project team goes back to step 2 or step 3 of the design process to improve the product. Once the user feedback is satisfied, these iterations continue while taking into account corporate frameworks (time and costs).

Top 10 User-Centered Design Principles

Principles of user-centered design attempt to guarantee that usability is the primary priority throughout the development process. These principles, if successfully followed, will ensure that user experience is fulfilled not just during the initial introduction of a product but also during its use.

Furthermore, each of the following principles may be tailored to match the specific requirements and interaction demands of any product.

1. Use Simple Language

Professional Web Designer strives to provide the most readable discourse for the user while creating a product. This involves clarifying vocabulary, eliminating jargon, and simply providing information pertinent to the work.

Presenting users with irrelevant information throughout their use of the product taints its usefulness. Furthermore, basic language helps the user finish the work without being overwhelmed or confused.

2. Feedback

Users expect a reaction to all of their actions. This might involve modifying the look of the screen after completing an activity. If the job is finished after some time, it should display a loading page to notify the user that the task is in process.

Keeping the user informed throughout the process reassures them and keeps them on track with their job.

3. Maintaining Consistency

Keeping the product consistent is essential in ensuring an ideal user experience. Consistency affects how customers approach a product, and the time it takes to learn how to use it.

From the start of the project until its completion, the consistent philosophy underpinning the UCD process should be maintained. If the interface design needs to be updated, it is critical to maintaining consistency across new features to stay beneficial to the user.

4. Give The Complete User Control

Consumers are already aware of their requirements. They should be able to use a product with minimal effort and depend on the product’s help to accomplish the rest.

By removing the effort from the job, the user can do it quickly while keeping control of their activities.

5. Describe The Situation

Before developing a product, the designer must first investigate the ideal user and their wants. The designers can gain a comprehensive sense of some of the issues these people experience by studying their lifestyles.

Many of these observations are conducted through interviews. These interviews provide the designer with information on the exact goals that users want to attain and how they want to achieve them.

6. Examine the Design

Designers undertake usability testing with actual users of their product at this stage in the UCD process. This stage provides designers with insight into how consumers will interact with the product and how to modify it to suit them better.

It is advised that this stage be completed as quickly as feasible. The sooner customers provide input, the faster designers can comprehend their product from the user’s perspective.

7. Create Designs That Are Specific To The Needs Of The User

The design team must examine the distinctive features of their intended demographic as well as frequent real-world activities while beginning the design process. Furthermore, the product should be appropriate for the environment in which it will be utilized the most.

Making a product that needs a lot of work from the user reduces its usability and usefulness, ultimately defeating the objective of UCD.

8. The Design Process Is Iterative

Because user-centered design is based on putting the user first, the product team should constantly be working to improve the user experience. By introducing changes gradually, you will gain a better understanding of your target audience.

9. Adequate Navigational Tools

An essential component of the user experience is the capability to navigate between pages of your website and return to the previous one. Make sure users know where they are on your website and how to leave any pages they don’t want to see.

Customers can better understand how to navigate your page by giving them features like a navigation map, for instance. Make it simple for customers to change their order without leaving the current page if they buy clothing and discover they need a different size once they reach the checkout page.

10. Unflawed System

Customers should find it easy to navigate between your website’s pages and accomplish their goals. If they make a mistake, be there to help them fix it so they can achieve their goal.

The form may ask for specific, essential fields, such as the square footage, and may also include a gentle reminder or an alert that appears if the user accidentally leaves a required field blank.

Customers may feel more comfortable responding to your prompts and participating in a conversation if you ask questions one at a time and offer automated responses for each response.

Wrapping Up

User-centered design is more than just making a good product. It goes further than that. You demonstrate your motivations and intentions by putting your users in the spotlight. You’re demonstrating that it’s not all about meeting deadlines or turning a profit. Instead, you’re telling your users that you understand what they want and prioritize their needs.

It should come as no surprise that the most effective teams are user-centric. Knowing your customer is essential for success in any industry, including design. Create products that put the user first, and you will create products that people will love.

You can build a more robust, user-friendly website that is better equipped to respond to user needs and expectations by incorporating the User Centered Design process into your product design. However, it’s crucial to collaborate with a specialist who can apply these techniques and produce the result you’ve envisioned.

 

Featured image by pch.vector on Freepik

Source

The post 10 Key Principles of User-Centered Design first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Popular Design News of the Week: June 20, 2022 – June 26, 2022

,

Every day design fans submit incredible industry stories to our sister-site, Webdesigner News. Our colleagues sift through it, selecting the very best stories from the design, UX, tech, and development worlds and posting them live on the site.

The best way to keep up with the most important stories for web professionals is to subscribe to Webdesigner News or check out the site regularly. However, in case you missed a day this week, here’s a handy compilation of the top curated stories from the last seven days. Enjoy!

How to Create Simple CSS Grid System

Why are You Running?

15+ VS Code Extensions for Web Developers

10 of the Biggest SEO Mistakes [Infographic]

SVG Loading Animations

AI Pixel Art Human Face

VSLook – Customize the Look of your VSCode

One Line of CSS to Add Basic Dark/light Mode

Basicons – Basic Icons for Product Design & Development

Touch-first Cursor: Round Pointers Vs Mouse Arrows

7 UX Laws You’re Probably Getting Wrong

“Google” Programmers – How One Idiot Hired a Couple More Idiots

Bunny Fonts – Privacy Respecting Drop-in Replacement for Google Fonts

Source

The post Popular Design News of the Week: June 20, 2022 – June 26, 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Case Study: Redesigning Todoist for Android

,

Todoist is a to-do list app that 25 million people rely on every day to keep their lives organized. As part of the Doist design team’s goals for 2021, we aimed to redesign the Todoist Android app to take advantage of the latest Google Material Design guidelines.

In this post, we cover the design decisions and processes behind redesigning the Todoist Android app for Material Design. We explore the Design and Android team’s collaboration practices that brought the app update to life, which resulted in winning the Material Design Award 2021 in the large screen category. Let’s get started!

Opportunity

When we started the project, our design implementation on Android was ready for a major overhaul. The last milestone redesign on Android was initiated after the release of the first Material Design guidelines in 2016. Since then the team successfully worked on continuous improvements to the Android app, but we saw the opportunity to improve Todoist on Android on a more holistic level.

We set out to clean up instances of older UI components, colors, and text styles and update them with the latest Material Design components. We observed that some interactions and navigational patterns had become inconsistent with what users were expecting on newer Android devices and were eager to modernize this experience. With new hardware and software changes in mind, we set out to make the experience on larger phones and tablets even better, so Todoist could take full advantage of the latest generation of devices. Material 2 and 3 provided an incredible new framework to rethink the current app experience. With this in mind, we set out to challenge what a modern Android app should look like and innovate on top of the default user experience.

Solution

The team set itself the goal of redesigning our Todoist Android app and aspiring to make it the best-designed productivity app on Android. The project was ambitious and scheduled to take several months to complete. We set ourselves the following targets while working on the project:

  • Review the current implementation and older design specs.
  • Study the latest Material Design Guidelines and assess what is relevant for our project.
  • Research great Material Design apps and case studies and learn from their execution.
  • Define the new Todoist Android app design language and document the changes.
  • Design and development work together to assess the proposed solution and implementation.
  • Test an early version of the new app internally to gather feedback and make adjustments.
  • Invite beta testers to the new app to gather feedback and make adjustments.
  • Refine the app and address core issues before launching to the public.

Review

The project was kicked off by reviewing the current Todoist Android app implementation, noting down what areas needed to be fixed and what was up to date. While reviewing, we took screenshots of the app implementation for reference. This way we could easily see the current state of the app and compare it to the new design proposals that would be created. Once the review process was finalized, we had a comprehensive overview of the current state of the app and the layout, component, and styling changes we wanted to make.

Study

We continued the project by studying the latest Material Design Guidelines, assessing the components and practices that were most relevant to Todoist.

When the project kicked off in February 2021, Material 2 was the most recent version of their design system. Since Material 2 had already been released for quite some time, we anticipated that design changes to Material would be announced soon at the Google I/O event in May 2021. Rather than wait, because we expected the changes to be iterative, we pushed ahead with our work.

We identified 25 components and UI patterns that we wanted to change across the app. The changes included buttons, forms, menus, sheets, navigation drawer, app bar, system bars, text and color styles, and more. We started by creating a table view in a Dropbox Paper document with the component changes and references links to Google’s Material Design Guidelines.

This components list was a starting point for discussion to plan the scope and complexity of the changes. Close async discussions between the design and development team in Twist and Dropbox Paper comments helped us make decisions about scope and complexity early on and set a solid foundation for the project.

Research

In the initial Material Design study, we also researched inspiring Material Design apps, Material studies, Play Store apps, and Google Workspace apps to learn from their execution.

We started out by studying the Material Design Award Winners 2020 and tested out the products that were showcased. The showcased winners struck a good balance between implementing the Material Design Guidelines while maintaining their own product’s brand within the system. This balance between Google’s guidelines and the Todoist brand was also key for us to get right and so we strived to find this mix across the work we created and implemented in the project.

Along with the MDA winners, we researched the Material Studies that Google produced to showcase what apps could look like with branding and Material Design guidelines applied. It was a great reference to see how far components could be customized while maintaining the core platform principles. The Reply case study in particular offered valuable insight to us as its content type and layout came closest to Todoist. It showcased how components like the app bar, navigation drawer, and large screen layouts worked while being customized.

We continued our research by searching the Google Play store for inspiring app examples. Google Tasks, Press, Periodic Table, and Kayak stood out to us as the level of polish and quality of the apps were on par with the experience we were aspiring to create.

Sometime later in the project when Material You was released (more on that later), we stumbled upon the Google Workspace apps blog post which previewed Material 3 changes that Google was introducing to their own products. It offered a great glimpse at what was to come before the Material 3 Design Guidelines were officially released. This post sparked new internal discussions and further design explorations that we considered for future Todoist Android updates.

Design Spec

As we started to define the new Todoist Android app design language and document the changes, we opted to create a design framework, focusing on creating components rather than designing every screen in the app. This allowed us to consistently apply the design system in the app. We did so by using the previously defined component list that we created during the review and study process.

Core screens from different areas of the app were chosen to demonstrate how the components could be applied. We chose to mock up the Todoist project view, navigation drawer menu, project view edit screen, settings, and project detail view, among others. These screens gave us a good overview of how buttons, forms, drawers, lists, and other components would work together and in different states; selected, pressed, disabled, etc.

During the project, we were transitioning our Doist design system to Figma and started creating our first components in the new Doist Product Android Library. We started by using some components from the Material Design UI kit – Components library from the official Google Figma resource file and added them to our Doist design system. We then continued to build up the Product Android Library file with our Todoist-specific components such as task list & board views, detail views, sheets, colors, typography, etc.

We continued by documenting color and typography changes that were based on the Material Design guidelines. The design team opted to implement a new Design Token framework that would share the same values between our design system and the development implementation. The development team would output the values they had in the current implementation and the design team would analyze which values were needed and which could be merged, changed, or deleted. This informed the new Design Token color and typography system which we then documented and discussed with the team to implement. Later in the project, we were happy to see a similar token system introduced by Material 3 in the latest guidelines which validated our thinking and principles behind the new design system.

The design documentation expanded to hold other edge-case mockups that could sit alongside the design system. We documented different responsive screen experiences between phones and tablets against the previous implementation. Additional sections were created to document the motion that should be used for certain components and screens by referencing existing Material Design guidelines examples or prototyping custom motion in Principle and After Effects. The design spec also touched on haptic feedback that should appear on touch targets, how dark mode should work across the new components, documenting Todoist themes within the new design language, and more.

Design Implementation

At Doist, the benefit of the squad is that cross-team collaboration is built into the make-up of the team. Designers, developers, support, and product managers work together in a squad to deliver the project. This close collaboration from the start is key to bridging the gap between scope, estimations, design, development, and delivery. The squad discussed their findings on a daily basis and came up with the best plan of action together.

Designers started by creating components in Figma and shared them with developers in Dropbox Paper. We used screenshots to document the current implementation next to the new designs and linked to the default Google Material Design components. This allowed the team to compare all references in one place. Developers shared their feedback, adjustments would be brainstormed together as the designs were iterated.

Designers on the project would share their work in progress on a weekly basis with the rest of the design team in a design review Twist thread. Here details about the designs were discussed, alternatives mocked up and bigger picture plans made. Design reviews brought up topics like FAB (Floating Action Button) placement, theme options, accent color usage on components, consistency with other platforms, navigation options, and shadow elevation. After thorough discussions and alternative mockups were presented, the design team aimed to find the right balance between Material Design and Todoist brand guidelines. The development team, also part of the design reviews, gave their feedback on the solution and raised technical complexities early on.

Eventually, the design was stabilized and consistencies updated across components and mockups. The design spec was kept up to date so the development team could always review the latest designs in Figma.

Testing

As soon as the development process started, the Android team provided early screenshots and videos in Twist threads while they were implementing the design spec. This practice allowed us to review the app implementation early and often. Designers could review the development work and share feedback in Twist, which resulted in getting the implementation to a high quality. Alongside Twist discussions, the team set up a Todoist project to track ongoing issues and fix bugs. Designers logged new issues, developers would solve them and share the new implementation for designers to review.

When the team had the first stable version of the Android app, we shared it internally at Doist to get more insight and feedback. Other Doisters could access the redesign via a feature flag that could be turned on in the app settings and test the new version for however long they wanted. The feature flag system allowed people to give us early feedback on the design decisions we made and report bugs. Feedback was submitted by the wider team through a dedicated Twist thread and designers and developers could discuss how best to address the feedback during the active project implementation.

After we refined the app implementation further and addressed early feedback we opened up the app update to our beta users. Here users had access to the new Android redesign and were able to give us feedback. Our support team gathered feedback and shared it with us in a dedicated Twist thread. The squad aimed to analyze every comment and looked for patterns where we could make tweaks and improvements to the user experience.

As part of these tweaks, we made changes to how the bottom bar and navigation drawer worked. Some users reported frustrations with the way the new bottom navigation and menu drawer worked. In its first implementation, the drawer was half raised when opened and had to be swiped up to be raised again to see the full content list. This was an issue for some users as it was slower to get to the content below the list. So we decided to fully raise the drawer by default when opening. We also made it easier to open the navigation drawer by sliding up from the bottom app bar. This was a small shortcut but it enabled users to get to their content faster.

Material You

While we were in the testing phase and about to wrap up the project, Google unveiled Material You, and sometime later the Material 3 Guidelines were published. With the newly announced resources, we went back to study the latest guidelines and references we could find to see where the Todoist Android app redesign fits in and which adjustments we might need to make now or in the future.

Dynamic Color was a big new feature that was announced as part of the Material You update. As Todoist supports many different themes the Material You Dynamic Color feature seemed like a good fit for our product. We decided to prioritize this feature and implement Dynamic Color light and dark themes as part of our Todoist theme settings options.

To implement Dynamic Color, the development team started off by creating a demo prototype that utilized the Dynamic Color system and showcased how we could select from a range of color choices that the system defined based on the wallpaper choice. From there, we tried to incorporate system behavior in our design mockups. We designed a range of different color mockups and components to see which ones could fit with which components. We then came up with a color system that worked for the Todoist app and the new themes. These new Dynamic Color themes would sit alongside our current theme options in the Todoist app settings. From here users could choose between Dynamic Color Light and Dark themes.

Along with Dynamic Color, the team also created a customizable bottom app bar, allowing users to set up the app in a way that’s most convenient to their workflow. The location of the Dynamic Add Button can be changed to the center, left, or right corner of the screen. The order of the Menu, Search, and Notification buttons can be rearranged to best fit the ergonomics of the user’s dominant (left or right) hand and optimize their navigation patterns.

Launch

As critical beta feedback was addressed and stability tweaks were made, the squad felt ready to release the new Todoist Android app to the public. The team logged the issues that could not immediately be addressed for future reviews and updates.

The design and marketing team readied the launch by creating What’s New banner artwork and copy that are displayed within the app when launching the update. The Doist marketing team also created release notes and shared the app update announcements on our social channels. The brand and product design team worked together to create custom image assets and copy that summarised the project work in a simple and beautiful way.

What’s Next: Material 3

After a successful launch of the redesigned Todoist for Android app, Google contacted Doist to announce that Todoist was selected as the Material Design Award 2021 winner in the Large Screen category. The team was excited to be recognized for their hard work and it felt like we achieved the goal we had set out to accomplish.

Internally, designers and developers continued to study and discuss the Material 3 updates. The design team started exploring mockups and design changes inspired by Material 3 and Google’s Workspace app updates. Some of our current Todoist explorations include changing the FAB styling, updating the app bar, further removing elevation shadows, and more. Here is a preview of what a future Todoist update could look like.

We hope these insights into Doist’s design process and collaboration practices have sparked your interest. Thank you for reading and stay tuned for future design updates!

Takeaways

  • Study the Material guidelines, Material Design winners, Material studies, and Google Workspace apps to make informed design decisions when designing your next product or app update.
  • Evaluate which Material Design components and practices are right for you and implement them into your product.
  • Carefully balance the Material Design guidelines with your brand guidelines to create a unique and consistent experience between your product and the platform it lives on.
  • Collaborate with your Android developers early and often to ship app updates efficiently and increase the design implementation quality.
  • Use design components and build a design system along with practical mockups to create an efficient design spec.
  • Consider how the latest Android features fit into your product and which have the most impact on your users before deciding to implement them.
  • Test and review builds with your internal team and external beta users to get valuable feedback and make adjustments before releasing them to the public.
  • Create announcement artwork to showcase your latest app or feature update along with a clear description to share in-app and on social media.

Source

The post Case Study: Redesigning Todoist for Android first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Popular Design News of the Week: February 14, 2022 – February 20, 2022

,

Every day design fans submit incredible industry stories to our sister-site, Webdesigner News. Our colleagues sift through it, selecting the very best stories from the design, UX, tech, and development worlds and posting them live on the site.
The best way to keep up with the most important stories for web professionals is to subscribe to Webdesigner News or check out the site regularly. However, in case you missed a day this week, here’s a handy compilation of the top curated stories from the last seven days. Enjoy!”

15 Websites with Inspiring Menu Design

Boardy – Dashboards for Everyone

42 Card Effects CSS for Websites

20 Best New Websites, February 2022

Move Over JavaScript: Back-end Languages are Coming to the Front-end

UI Generator – Get Mockup UI in Seconds

50 Cool Web and Mobile Project Ideas for 2022

These are the Highest-paying Design Jobs in 2022

Top Trends in Product Design for 2022

Pppointed – SVG Arrow Maker for all Kinds of Decorative Arrow Styles

Simple.ink – Build Websites with Notion in ~10 Sec

The React Cheatsheet for 2022

 

Source

The post Popular Design News of the Week: February 14, 2022 – February 20, 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

What is the “Minimum” in Minimum Viable Product?

,

“Minimum Viable Product,” or “MVP,” is a concept of agile development and business growth. With a minimum viable product, you focus on creating the simplest, most basic version of your product, web application, or code possible.

Minimum viable products include just enough features to attract early adopters and validate your idea in the early stages of the development lifecycle. Choosing an MVP workflow can be particularly valuable in the software environment because it helps teams receive, learn from, and respond to feedback as quickly as possible.

The question is, how exactly do you define the “minimum” in MVP? How do you know if your MVP creation is basic enough while still being “viable”?

Defining the Minimum Viable Product: An Introduction

The concept of “Minimum Viable Product” comes from the Lean Start-up Methodology, introduced by Eric Ries. The purpose of MVP is to help companies quickly create versions of a product while collecting validated insights from customers for each iteration. Companies may choose to develop and release minimum viable products because they want to:

  • Introduce new products into the market as quickly as possible;
  • Test an idea with real users before committing a large budget to product development;
  • Create a competitive product with the use of frequent upgrades;
  • Learn what resonates with the target market of the company;
  • Explore different versions of the same product.

Aside from allowing your company to validate an idea for a product without building the entire concept from scratch, an MVP can also reduce the demand on a company’s time and resources. This is why so many smaller start-ups with limited budgets use the MVP and lean production strategy to keep costs as low as possible.

Defining an MVP: What your Minimum Viable Product Isn’t

When you’re building a Minimum Viable Product, you’re concentrating on developing only the most “essential” features that need to be in that product. For instance, you might be building a shopping app for a website. For the app to be “viable,” it would need to allow customers to search through products and add them to a basket or shopping cart. The app would also need a checkout feature and security components.

However, additional functionality, like the ability to send questions about an item to a customer service team or features that allow clients to add products to a “wish list,” may not be necessary straight away. Part of defining a minimum viable product is understanding what it isn’t. For instance, an MVP is not:

  • A prototype: Prototypes are often mentioned alongside MVPs because they can help with early-stage product validation. However, prototypes are generally not intended for customers to use. The “minimum” version of a viable product still needs to be developed enough for clients and users to put it to the test and provide feedback.
  • A minimum marketable product: An MVP is a learning vehicle that allows companies to create various iterations of an item over time. However, a minimum marketable product is a complete item, ready to sell, with features or “selling points” the company can highlight to differentiate the item from the competition.
  • Proof of concept: This is another similar but distinct idea from MVP. Proof of concept items test an idea you have to determine whether it’s attainable. There usually aren’t any customers involved in this process. Instead, companies create small projects to assess business solutions’ technical capabilities and feasibility. You can sometimes use a proof of concept before moving on to an MVP.

Finding the Minimum in your MVP

When finding the “minimum” in a minimum viable product, the primary challenge is ensuring the right balance. Ideally, you need your MVP to be as essential, cost-effective, and straightforward as possible so that you can create several iterations in a short space of time. The simpler the product, the easier it is to adapt it, roll it out to your customers, and learn from their feedback.

However, developers and business leaders shouldn’t get so caught up focusing on the “Minimum” part of Minimum Viable Product that they forget the central segment: “Viable”; your product still needs to achieve a specific purpose.

So, how do you find the minimum in your MVP?

1. Decide on Your Goal or Purpose

First, you’ll need to determine what your product needs to do to be deemed viable. What goal or target do you hope to achieve with your new product? For instance, in the example we mentioned above, where you’re creating an ecommerce shopping app, the most basic thing the app needs to do is allow customers to shop for and purchase items on a smartphone.

Consider the overall selling point of your product or service and decide what the “nice to haves” are, compared to the essential features. For instance, your AR app needs to allow people to interact with augmented digital content on a smartphone, but it may not need to work with all versions of the latest AR smart glasses.

2. Make a List of Features

Once you know the goal or purpose of your product, the next step is to make a list of features or capabilities you can rank according to importance. You can base your knowledge of what’s “most important” for your customers by looking at things like:

  • Competitor analysis: What do your competitors already offer in this category, and where are the gaps in their service or product?
  • User research: Which features or functionalities are most important to your target audience? How can you make your solution stand out from the crowd?
  • Industry knowledge: As an expert in your industry, you should have some basic understanding of what it will take to make your product “usable.”

3. Create Your Iterations

Once you’ve defined your most important features, the next stage is simply building the simplest version of your product. Build the item according to what you consider to be its most essential features and ask yourself whether it’s serving its purpose.

If your solution seems to be “viable,” you can roll it out to your target audience or a small group of beta testers to get their feedback and validate the offering. Use focus groups and market interviews to collect as much information as possible about what people like or dislike.

Using your feedback, you can begin to implement changes to your “minimum” viable product to add more essential features or functionality.

Understanding the “Minimum Viable Product”

Minimum viable products are evident throughout multiple industries and markets today – particularly in the digitally transforming world. For instance, Amazon might be one of the world’s most popular online marketplaces today, but it didn’t start that way. Instead, Jeff Bezos began purchasing books from distributors and shipping them to customers every time his online store received an order to determine whether the book-selling landscape would work.

When Foursquare first began, it had only one feature. People could check-in at different locations and win badges. The gamification factor was what made people so excited about using the service. Other examples include:

  • Groupon: Groupon is a pretty huge discount and voucher platform today, operating in companies all around the world. However, it started life as a simple minimum viable product promoting the services of local businesses and offering exclusive deals for a short time. Now Groupon is constantly evolving and updating its offerings.
  • Airbnb: Beginning with the use of the founders’ own apartment, Airbnb became a unicorn company giving people the opportunity to list places for short-term rental worldwide. The founders rented out their own apartment to determine whether people would consider staying in someone else’s home before eventually expanding.
  • Facebook: Upon release, Facebook was a simple social media tool used for connecting with friends. Profiles were basic, and all members were students of Harvard University. The idea quickly grew and evolved into a global social network. Facebook continues to learn from the feedback of its users and implement new features today.

Creating Your Minimum Viable Product

Your definition of a “minimum viable product” may not be the same as the definition chosen by another developer or business leader. The key to success is finding the right balance between viability – and the purpose of your product, and simplicity – or minimizing your features.

Start by figuring out what your product simply can’t be without, and gradually add more features as you learn and gain feedback from your audience. While it can be challenging to produce something so “minimalistic” at first, you need to be willing to release those small and consistent iterations if you want to leverage all the benefits of an MVP.

Suppose you can successfully define the meaning of the words “Minimum” and “Viable” simultaneously with your new product creations. In that case, the result should be an agile business, lean workflows, and better development processes for your entire team.

 

Featured image via Pexels.

Source

The post What is the “Minimum” in Minimum Viable Product? first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

How to Get Started with the MVP Workflow

,

Few things are more important to a web designer or developer’s chances of success than having the proper workflow. The term “workflow” applies to the set of standardized steps you or your company uses to create, test, and deploy designs or products.

Over the years, as development processes have evolved, so too have the workflows experts use to bring their ideas to life. The MVP workflow, or “Minimum Viable Product” strategy, is one of the most popular options in 2022.

Here’s what you need to know about the MVP workflow and how it differs from some of the other standard workflows developers may be used to.

What is the Designer/Developer Workflow?

As mentioned above, the designer/developer workflow is a series of steps used by experts in the web design world to achieve a creative goal. The process includes the steps taken to start a project, evolve it, and finish it. Since software is never developed without tools, the technology you’ll access throughout the development process is also considered in most workflows.

An example of a standard development workflow might look like this:

  • Scaffolding: This is the stage wherein you start your new web project, creating a git repo, downloading libraries, preparing file structures, and completing other tasks to make sure your product is ready to roll out into the world.
  • Develop: This is where you’ll spend most of your time writing code for your application or website. The development process may include various specific tools and support from other staff members.
  • Test: In this stage, you examine the functionality of your code to determine if everything works as it should. If there are errors or issues, you can go back and develop fixes to the potential problems. Your code may go through the development/test process several times before you can move to the next stage.
  • Integrate: This is when you merge the code for your part of the development process with the rest of the team. You can also integrate your code into websites and existing apps at this point. If you’re working solo, you can skip this process.
  • Optimize: You prepare all your assets for use on a production server during the optimization stage. Files are generally optimized to ensure your visitors can view your site easily or access your applications with ease.
  • Deploy: In the deployment stage, developers push code and assets up into the server and allow for changes to be viewed by the public.

What is MVP? (Minimum Viable Product)

Now you know what a developer workflow looks like, you can begin to assess the concept of the “MVP” workflow. The term “MVP” stands for Minimum Viable Product.

The idea of “Minimum Viable Product” applies to a range of industries, from education to healthcare and government entities. This term comes from lean start-up practices and focuses heavily on the value of learning and changing during the development process.

When you adapt your workflow to focus on an MVP, you’re essentially adjusting your focus to a point where you can create a stripped-back version of something new – like an app or a website. The MVP is built just with the core features (the minimum), so you can bring the idea to market and test it as quickly as possible.

For instance, if your goal were to create an attractive new website for a client, an MVP would focus on implementing the crucial initial tools, and nothing else. While you may create checkout pages, product pages, and other aspects of the site, you wouldn’t populate it with content or start experimenting with bonus widgets and apps.

So, how does this offer a better alternative to the standard workflow?

Simply put, an MVP workflow is quick, agile, and easy. The idea is you can validate key concepts with speed, fail quickly, and learn just as fast. Rather than having to build an entire app and almost start over from scratch every time you find an error, you can race through the iteration and development process.

MVP workflows are also highly appealing to start-ups and entrepreneurs hoping to validate ideas without a massive amount of upfront investment.

Examples of MVP Workflows

Still confused? The easiest way to understand how an MVP workflow works is to look at an example.

Let’s start with a conceptual example. Say you were building a voice transcription service for businesses. The desired features of this product might include the ability to download transcription, translate them into different languages, and integrate them into AI analytics tools.

However, using the MVP approach, you wouldn’t try to accomplish all of your goals with your software at once. Instead, you’d focus on something simple first – like the ability to download the transcripts. Once you confirm you can do that, you can start a new workflow for the next most important feature for the app.

One excellent example of a company with an MVP approach is Airbnb. The entrepreneurs behind this unicorn company, Joe Gebbia and Brian Chesky, didn’t have a lot of cash to build a business with at first. They had to use their own apartment to validate the idea of creating a website where people could share their available “space” in a home or apartment with the public.

To begin, Airbnb only created a very basic website, published photos of their property, and waited to see the results. After discovering people were genuinely interested in renting another person’s home, the company was able to begin experimenting with new ideas to make a site where people could list their properties for travelers.

The Pros and Cons of an MVP Workflow

There are a lot of benefits to the MVP workflow – particularly when it comes to gaining agility and developing new products quickly. However, there are downsides too.

Pros

  • With an MVP approach, you can maximize your learning opportunities and create a more innovative, successful product at speed. You get to test every step of the way.
  • You release iterations or versions of your product quickly, which means you discover problems faster, allowing you to quickly solve these issues.
  • You build on the benefits of customer fans, “evangelists” in the marketplace who are keen to help your product or service grow.
  • An MVP gives you more freedom to try out unique ideas and “risks” you might otherwise avoid with a traditional workflow.
  • Because you’re focusing on creating only the “minimum viable product,” you don’t have to spend a fortune on initially setting up your workflows.

Cons

  • Agile work with an MVP flow requires a lot of effort in collecting constant feedback from customers and releasing iterations.
  • You’ll need to dedicate yourself to releasing many small and frequent product releases on a tight schedule.
  • You might have to revise the functionality of your product or app a number of times.

Creating Your MVP Workflow

If you believe an MVP workflow might be effective for you, the first step is defining your “Minimum Viable Product.” The app, website, or product you design needs to align with your team’s strategic goals, so think about what your company is trying to achieve at this moment – before you get started. If you have limited resources, or specific purposes, like improving your reputation as a reliable company, now might not be the right time to develop a new MVP.

Ask what purpose your minimum viable product will serve and what kind of market you’re going to be targeting. You’ll need to know your target customer to help you test the quality and performance of each iteration of your MVP. Once you know what your ideal “product” is, ask yourself what the most important features will be.

You can base these decisions on things like:

  • User research
  • Competitive analysis
  • Feedback from your audience

For example, if you’re producing an AI chatbot that helps companies to sort through customer inquiries, the most important “initial feature” may be the ability to integrate that bot into existing websites and apps owned by the company.

MVP Approach Guidelines

Once you have your hierarchy of most valuable features for your minimum viable product, you can translate this into an action plan for development. Remember, although you’re focusing on the “minimum” in development, your product still needs to be “viable.” In other words, it still needs to allow your customer to achieve a specific goal.

  • Review your features: Reviewing your prioritized product requirements and the minimum level of functionality you can deliver with each of these “features.” You need to ensure you’re still providing value to your customer with anything you produce.
  • Build your solution: Build your minimum set of features for the product or service. Remember to build only what is required. You can use methodologies like the agile or waterfall method to help guide your team during this process.
  • Validate your solution: Release your offering into the market, and ensure you have tools in place to gather feedback from early adopters. Use beta programs, focus groups, and market interviews to understand how your solution works for your customers and where you can improve on your current offer.
  • Release new iterations: Based on what you learn from your target audience, release improvements to your product quickly. Use your validation strategies to collect information from your audience with each release.
  • Review again: Go back to your product requirements and desired features and start the process over again, this time focusing on the next most valuable functionality. Over time, the value of your minimum viable product will increase.

Using the MVP Workflow Approach

While the MVP workflow approach might not be the right solution for every development or design team, it can work very effectively in the right circumstances. The MVP approach doesn’t minimize the importance of understanding market problems and delivering value. Instead, the focus is on delivering quick value that gradually increases and evolves over time.

As many developers and designers know, the most useful form of product validation in most cases is real-world validation. When your customers have had an opportunity to use a product on a day-to-day basis, they can provide much more effective feedback.

Just keep in mind that committing to the MVP approach also means changing your workflow and committing to iterations – otherwise, other features may never be completed. You’ll need to be willing to work quickly and in small bursts without getting too heavily caught up in one feature or functionality.

 

Featured image via Pexels.

Source

The post How to Get Started with the MVP Workflow first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Ranked: Top 10 Illustration Apps in 2021

,

Illustration is a big trend in 2021. Every designer should have some ability to illustrate, whether that’s producing icons, creating lettering, mocking up layouts, or crafting full-blown illustrations.

Designers’ workflows are as varied as their work, and one designer’s favorite tool is a frustrating mess to the next designer. Most design apps have a free trial, so it’s worth trying out a few before committing.

Counting down to the best illustration app for designers in 2021, all of the apps on this list are worthy of at least a second glance:

10. Vectr

Vectr is a simple vector design tool. It is heavily geared towards layout and even product design. It’s difficult to use it for many illustration jobs, but simple icon and UI creation are possible. It scrapes into our top ten thanks to the fact that it’s free to use.

9. Paper

Paper is a sketching app developed by WeTransfer. It grabs number nine in our top ten thanks to its simplified interface that is perfect for generating ideas. It may not be the most flexible app, but it’s free to download, making illustration accessible to anyone with an iOS device.

8. Inkscape

We love the fact that there’s someone out there producing a professional-grade artwork app for free. Inkscape is available for GNU/Linux, Windows, and macOS. If you’re interested in exploring this design area without signing up for a subscription or buying an iPad, Inkscape is a great place to start.

7. Assembly

Assembly is another app that’s dependent on the transition of illustrators from desktop machines to mobile devices and is available for iOS. Assembly does things a little differently; instead of manipulating boolean curves, Assembly builds illustrations out of shapes. If you’re someone who thinks they can’t draw (spoiler alert: everyone can draw), this is the app for you.

6. Sketch

It’s a shock low-rating for Sketch, the highly popular product design app doesn’t make it out of the bottom half of our list. The reason for the lower ranking? Sketch is an incredible design app, but its greater investment in prototyping features has come at the cost of drawing innovation. It’s still a great choice for crisp icon design, but it’s not flexible enough to take a higher spot in our list.

5. CorelDRAW

If you’re getting the impression that design apps are mostly for macOS or iOS, then you’d not be alone. CorelDRAW Graphics Suite is one of the few that began its life on Windows before being rebuilt for Mac. CorelDRAW is a premium option, but like Adobe’s offering, it is a suite of tools that cover everything you’ll need to create any form of design work you could ever need.

4. Vectornator

Moving closer to the top spot, Vectornator is an up-and-coming tool. Like many other apps further up our chart, Vectornator does a lot more than simply illustration. Its underlying tools provide a solid foundation for a flexible set of tools that you can use for any artwork. Vectornator does an awful lot, awfully well. 

3. Procreate

Procreate is one of the finest apps on this list, thanks in main to its incredible brush studio; being able to edit the marks you make is essential for any expressive artwork. Procreate enables expressive illustration, typography, and simple sketches. The only downside to this app is that it’s iOS only; if available on more platforms, it might have been even further up the list.

2. Adobe Illustrator

That’s right; we don’t think design giant Adobe’s illustration app Illustrator is worthy of the number one spot.

Illustrator is an excellent tool and arguably deserves to be considered Adobe’s flagship product. Since Adobe relented and allowed individual app subscriptions, it is also reasonably priced. It does everything you could want in an illustration app, from designing icons to creating original artwork.

So why not the top spot? It wasn’t so much that Illustrator fell down anywhere, as a different app pipped it to the post…

1. Affinity Designer

The best app for illustration in 2021 is Affinity Designer. We’ve been fans since its first beta version, and we’ve watched it go from underdog to champion.

On top of being an excellent vector app, Designer is comfortable with raster graphics. Although it certainly can’t compete with Photoshop (Affinity built Photo for that), Designer is more than adequate for many image tasks, making it a great all-around design app. Designer was also the first design app to support macOS’ new M1 chip natively.

The knockout blow is that Affinity Designer is available as a desktop app and an iOS app; the two apps have minor differences in their interfaces; what matters is that both apps use the exact same file format. You can seamlessly switch between desktop, iPad, and back to desktop, taking advantage of the precision of a mouse and the expression of a stylus.

It’s this kind of flexibility that bends Affinity Designer to your workflow instead of the other way around, and that’s why it’s top of our list.

Source

The post Ranked: Top 10 Illustration Apps in 2021 first appeared on Webdesigner Depot.


Source de l’article sur Webdesignerdepot

/par