“Opening our Toronto office marks an exciting milestone in our growth. After four years of partnering with Canadian clients, we’re investing locally to deliver faster response, deeper understanding of Canadian user needs, and to expand our work in AI-driven product strategy and design.”

– Mark Baldino, Co-Founder of Fuzzy Math Inc.

Canada’s IT services market is projected to grow from approximately USD 60 billion in 2025 to more than USD 128 billion by 2030, nearly doubling in size with an average annual growth rate of over 16%. Toronto, the country’s largest technology hub, is a natural choice for Fuzzy Math’s expansion, offering access to world-class talent and proximity to enterprise clients.

Toronto was ranked 4th in specialized AI talent and is home to 40% of Canada’s AI companies, making it the ideal market to continue Fuzzy Math’s AI-driven product strategy and design.

“Fuzzy Math has been instrumental in helping us reimagine how digital, UX, and AI come together to serve clients better. Their new Canadian office amplifies that impact — giving our teams and clients local access to a trusted partner who understands both the pace of innovation and the importance of human-centred design.”

– Davin Gnanapragasam, CTO and Partner, Tax & Legal at KPMG Canada

Toronto Global, the region’s investment attraction agency, supported Fuzzy Math in establishing its presence in the Toronto Region by providing market insights and guidance throughout the expansion process.

“Toronto is North America’s fastest-growing tech hub and a magnet for global companies looking to innovate and scale. Fuzzy Math’s decision to establish a Canadian office here is another strong signal of confidence in our region’s world-class design and technology talent. We’re thrilled to welcome them to Toronto’s thriving innovation ecosystem.”

– Stephen Lund, CEO of Toronto Global

Canadian organizations interested in exploring how Fuzzy Math can support their digital, UX, and AI initiatives are invited to book a consultation with Co-Founder Mark Baldino during his time in Toronto. To schedule a meeting, please contact mark@fuzzymath.com or schedule time direct here.

About Fuzzy Math

Fuzzy Math (www.fuzzymath.com) is a user experience design consultancy that helps B2B software companies and enterprise organizations unlock innovation through UX design, product strategy, and applied AI. With a track record of delivering complex design solutions for financial services, technology, healthcare, and government organizations, Fuzzy Math’s team blends design thinking, research, and technical expertise to create products that drive adoption and measurable business impact. Founded in Chicago in 2009, Fuzzy Math now operates in both the United States and Canada.

Full Release here: https://www.newswire.ca/news-releases/fuzzy-math-inc-opens-toronto-office-tapping-into-thriving-canadian-tech-market-847166728.html

The post Press Release: Fuzzy Math Opens Toronto Office, Tapping into Thriving Canadian Tech Market appeared first on Fuzzy Math.

AI is transforming digital products—but where should it fit in your user experience? In this UX Masterclass, Mark Baldino, co-founder of Fuzzy Math, breaks down how User Journey Mapping can reveal the best places to integrate AI meaningfully and effectively.

What You’ll Learn:

• What User Journey Mapping is and how it helps identify AI opportunities
• How to analyze your journey map for unmet expectations, friction points, and time-intensive tasks
• The difference between AI automation vs. augmentation
• The strengths and weaknesses of AI in UX design
• Key considerations for designing AI-powered features, including trust, accuracy, data, and technical feasibility AI is a powerful tool, but it’s not a one-size-fits-all solution.

Learn how to integrate AI thoughtfully to enhance user experiences and avoid common pitfalls.

Need expert help? Reach out to the Fuzzy Math team to bring AI-powered UX to your digital products: http://www.fuzzymath.com

Keywords: UX Design, AI in UX, Journey Mapping, AI-Powered UX, AI & Product Design, UX Strategy, AI Automation, AI Augmentation, AI User Experience, B2B UX, Enterprise UX, AI Design Thinking, UX Masterclass, Digital Product Design

Transcript

[00:00.3]
Hi, I'm Mark Baldino. I'm the co founder of fuzzymath. Fuzzy Math is the user experience design consultancy that brings consumer grade UX to business applications for B2B and enterprise tools. Today we're covering a bit of a first at Fuzzy Math. We're doing a UX Masterclass. My intent with this masterclass is to take my 25 years of UX design experience and a multitude of years of experience on my team and get it out of our heads into the wider community.

[00:24.3]
For this masterclass, I want to continue on a topic I've recently covered on my podcast, UX Leadership by Design. That topic is AI in Design or more accurately for this class, Designing for AI. In recent episodes I've talked about some of the really transformative ways that AI can be used in design.

[00:40.7]
Stands to reason that it's going to be a hot commodity for businesses looking to integrate AI tools into existing digital products. Our topic to guide you along the way is a powerfully simple UX artifact, the User Journey Map, and how to find those gaps in your user experience where AI can be the most impactful and meaningful.

[01:00.1]
Okay, so a definition User Journey Map is a visual representation of a user's experience with a product or service over time. It highlights key touch points, emotions and pain points, helping teams understand user needs and identify opportunities for improvement. We know that design is often about storytelling.

[01:17.1]
Stories make it easier to understand and empathize with users, and they make it easier for whole teams to remember complex processes and share them with others. The Journey Map is a deliverable to tell a story, and along the way we can find ways to slot in AI for your product to support the user journey.

[01:36.6]
Before we get too deep into the analysis of journey maps, I think it's important to examine AI itself and its strengths and weaknesses to allow you to make better decisions regarding what it can do for your users. For example, whether you should use AI to fully automate a user process or simply automatically augment it.

[01:54.5]
The strengths of AI lie in its ability to parse huge amounts of data, quickly, define things, synthesize things, and predict things. Not to mention, as a robot, it's not going to care very much if it has to do the same task a million times. A human, however, would very much care and probably quit for this reason.

[02:14.0]
AI can be a great time saver and bring lots of efficiency. But there are weaknesses of AI as well. Namely, it represents a technology that is, you know, as a whole in its infancy. Think of which plane you'd rather take a trip on a canvas clad biplane from 1950 or a modern airliner, AI is closer to the biplane than to the airliner.

[02:34.0]
What this means in practice is that AI will have difficulty always being able to present the correct answer in some of its predictions. AI also requires users to communicate with them in fairly specific ways,  so much so that there are even classes on prompt generation. Okay, so with these concepts of AI in mind, let's turn back to our journey mapping and how to utilize them to determine where AI can meaningfully improve your user journey.

[03:02.9]
So there's three ways to analyze journey maps for this situation. Areas of unmet expectations, areas where there's large friction points and areas that are time intensive for humans. The first, areas of unmet user expectations.

[03:19.3]
So let's put some AI into an unmet expectation. Imagine you have a dashboard with users, and users land upon it when they enter your platform. And your service has many different and complex user types with many different permissions and needs. If the page is too generic and does not meet the specific need of a user in their role, sort of have an unmet expect unmet expectation.

[03:40.5]
We have a gap between their experience and the reality, their expected experience and the reality. So how can AI help? Why not? You use AI to analyze sort of users complex webs of permissions and responsibilities on the fly and entirely in the background.

[03:55.7]
Set up a dashboard that is customized for them upon login. But later we'll cover whether or not you want to, you know, integrate that feature and how you go about designing and building it. But let's move next onto the next aspect of journey map analysis and that's areas of large friction points. So this is one of the easiest things to identify because they stick out like a sore thumb or like a downward slope with a red sticky on it in the journey map.

[04:18.2]
And that's, you know, when users have large friction points. And these are mostly measured in user pain and frustration. Thinking about AI to address friction points depends on where the friction stems from. For example, perhaps friction stems from a user have to look through hundreds of spreadsheets and find certain data points needed for their job.

[04:34.1]
That smells like an AI task to me. The third and final is high time usage. So this last point I want to cover is a big one because it speaks to a big strength in AI. It's where in your journey maps you're seeing that areas of time intensive effort for your users. Spending large amounts of time could easily be related to unmet expectations and friction points, but not always.

[04:53.6]
Where AI fits in depends on the concepts of positive time spent and negative time spent. Positive time spent is time a user spends on something that increases their positive feelings. You want to increase these, you want to amplify these. Negative time spent is large time usage that is frustrating, difficult or stressful for users.

[05:11.5]
You want to decrease these naturally. So here's an example. Fuzzy math is full of designers and a big part of a UX designer's job is to conduct research, take all the data, comb through it, organize and synthesize it. You could argue that this would be a negative time process. It takes a long time, it's pretty difficult. It can be stressful especially if you're in a time crunch.

[05:28.5]
So when I just remove it and let AI do the synthesis. I asked a few of my designers on the team and each one of them said that no matter what AI could do here, they'd still want to undertake the manual process of data analysis and synthesis that entails that part of the design process themselves.

[05:44.5]
They want to do it and they feel like they need to do it to make better design decisions. So it's just a word of caution. Don't try to replace something your users need or want to be doing with AI. Maybe consider augmenting or assisting but thoughtfully of how and where. Don't always move to automate and replace.

[06:03.4]
Okay, so you built your user journey map. You've carefully weighed and considered each node in the user's journey and ask yourself, does AI fit here with any of AI's inherent strengths? Will my users want this in their process? Should the AI replace this process or simply augment it?

[06:20.4]
And congrats, you've arrived at an answer. You do want to put AI into your product. So what are the considerations for the design and implementation of an AI feature in your product? Product? There's four I want to cover. First is user needs and user experience. The second is trust and accuracy.

[06:35.7]
The third is data, and the fourth is technical feasibility. Okay, so the first one, user needs and user experience. It really shouldn't come as a surprise that the consideration we begin with is user needs and user experience when using an AI tool. We are, after all, a UX design consultancy and we very much believe in the power of user centered design, especially when making features for complex B2B platforms.

[06:58.5]
So start and end your process with this question. Is this a true unmet need? Maybe consider, does it contribute to the five tenants of usability, satisfaction, memorability, efficiency, effectiveness and learnability? Will this be a meaningful and impactful change?

[07:14.4]
Which brings us to trust and accuracy. We talked about the limitations and weaknesses of AI. We mentioned that AI models might not always be accurate. AI systems are probabilistic. So where a human might look at data and say, well, that's obviously wrong and AI model might dictate that answer A is more probable over answer B.

[07:30.9]
The solution to this problem is being transparent about AI's capabilities, sourcing where the data is from, helping the AI model build trust by clarifying where it might be accurate and where it might struggle. So will acknowledging this make users trust your model less? Maybe, let's be honest. But nothing will tank user trust more than pretending the AI is infallible and letting the user be disappointed to learn when it's wrong.

[07:51.6]
Which brings us to some more pragmatic components of considering an AI feature. Three, data. And four, technical feasibility. Who's going to build and train this amazingly well designed, clever AI tool? Where's the data coming from? Do we have it already? Do we need to collect it and organize it?

[08:06.7]
Or do we need to source it from a third party? Do we have a team of developers and data scientists who can move this forward? What's the technical feasibility? What is the cost benefit to your product and to your business if you focus on this AI feature versus a non AI feature? There's so much that goes into this decision making process even before you build.

[08:23.3]
There are many ways your design team can work with data science and engineering that maybe it should be a masterclass of its own. Maybe it will be. But in conclusion, we've covered a lot here, from the creation of user journey maps to three ways to analyze them to find the right spots to integrate AI and into the four considerations for designing and building those features.

[08:43.3]
It is a lot, but you should not be overwhelmed to launch AI into your product. There are clear and concrete steps to take to integrating AI in meaningful and impactful ways. Unlike many products, features and tools, once they're released they need to be monitored and iterated upon.

[08:59.6]
AI certainly needs monitoring. Is it giving your users the right feedback or help? Is it being trained correctly by users responses? Is it giving people sensitive or inappropriate information? Quality assurance work goes a long way with everything, but especially with AI, of course, an offer if you're about to undertake the process of integrating AI into your product, or you've started and you think you could use a little bit of help, please feel free to reach out to me and the team at Fuzzy Math.

[09:24.2]
Maybe leave a comment below on how your own journey is going. And of course, if you have any feedback on this masterclass, please reach out. Until next time, thank you for watching. I'm Mark Baldino and this has been the first Fuzzy Math UX masterclass.

The post UX Masterclass: Journey Mapping for AI-Driven Experiences appeared first on Fuzzy Math.

Why choose a custom dashboard?

It’s the classic build vs buy conundrum of whether to develop a custom dashboard or buy a templated dashboard. Third party tools like PowerBI do work well as a hybrid solution to pulling data and displaying it in a custom format. The challenge arises when existing solutions don’t provide clients with the level of data exploration needed to take actionable next steps.

Mark Baldino, co-founder of Fuzzy Math details why a custom dashboard solution may be right for you:

The post Crafting Personalized Dashboards with Fuzzy Math appeared first on Fuzzy Math.

The tools we use!

2023 was a big year for a lot of the tools that designers use everyday – from figma updates, to the continuing improvement of ‘no code tools’, to AI support – this year felt like we were getting updates to our toolkit every month.

Starting with Figma!

The post Fuzzy Math 2023 WRAPPED! appeared first on Fuzzy Math.

So what exactly is DesignOps?

DesignOps is a set of practices and principles aimed at streamlining and improving the design process within an organization. You can think of it as steps an organization can take to measurably improve a design team’s performance and its impact to the business. It is especially important to operationalize design practices since design is an area that can still be misunderstood, poorly integrated, and not well supported within many businesses.

At Fuzzy Math, we believe that in order to deliver exceptional user experiences, businesses need to set up design processes that promote creativity, efficiency and more streamlined integration. In addition, design team members should be enabled and empowered to do their best work. DesignOps is a tool to help optimize your UX design team, and ensure they are working in the best ways to support your business. In this article, we will explore why DesignOps is important, and how to best implement it within your business to help achieve success.

Why is DesignOps Important for your Business?

Right people, right seat

Setting up design operations can benefit your business in a variety of significant ways. Firstly, it ensures the right people are in the right roles. As design teams grow, DesignOps helps to identify which roles are needed, which skill sets are necessary for that role’s success, and helps to ensure the right people are hired to best sustain the team and project needs. When you are more aware of the design team make-up and skill set, you can better resource projects to align with skills and availability. This helps to avoid burnout from people being over-resourced, and increases productivity due to clearer assignments. If you aren’t at a place to invest in growing your design team, DesignOps can also better enable your current team to do their best work through increased motivation, efficiency, and alignment. It can help ensure that your design training is relevant and accessible, avoid redundancy of more than one person taking on the same responsibility, and help separate teams or team members work better together. This leads to getting more, higher quality output from your team without increasing headcount. It also helps keep the talent that you have since designers are able to make more impact, have clearer purpose, and are assigned to teams and tasks that align with their skills. Through the incorporation of DesignOps, the design team is aligned on their roles and responsibilities, and supported within their roles in order to do their best work.

Consistent, efficient, and scalable processes

Once you have the right people to do the work, DesignOps can also help ensure that work is done efficiently and sustainably. By establishing standardized workflows, tools, and guidelines such as design systems, designers can produce consistent design outputs more quickly and at a higher quality. Without this type of shared documentation, businesses risk design assets being made in silos, causing inconsistency and frustration from designers by accidentally re-doing something that was already done. Having a design system is necessary to ensure higher quality control, and can help reduce the time and effort spent reviewing and ensuring each design matches an organization’s standards. Establishing processes that encourage collaboration and feedback also helps ensure that the work that is being done is alignment with what is needed, and can be completed within the proper timeline. This can include regular design reviews to iterate and align earlier in the design process before moving too far in the wrong direction at a high fidelity.

Another important process to establish within your organization is user research. ResearchOps is an aspect of DesignOps that helps ensure research is done with intention so that designs are user-centered and impactful. This is particularly important to ensure design can solve the right problems based on the user experience itself, instead of being utilized to help make smaller, bug fixes. ResearchOps helps create a shared understanding of the larger opportunities for the product and service which leads to higher impact solutions. It helps create a design process that is proactive instead of reactive. When research is implemented at the right time and in a meaningful way, designers can create designs that are more aligned with your customer needs and goals – thus driving sales and customer retention.

Aligned with business goals

Lastly, DesignOps can help the entire organization better understand the purpose and impact of design, and create a shared culture around the user-centered process. Through the establishment of metrics, the design team can measure their impact to the user experience and the overall success of a product or service. Metrics can also highlight the importance of a design practice to other roles and teams within the business. Just like any other team within your organization, your design team should have a clear mission and an understanding of how their team directly contributes to the organization’s success. When that mission is properly communicated and understood, designers better understand how their work fits into the bigger picture and feel more respected and valued as a result. DesignOps can create a shared culture among the team, increasing camaraderie and a sense of belonging to your organization.

How Fuzzy Math Implements DesignOps for Our Clients

As an organization dedicated to UX design for over 15 years, Fuzzy Math has developed proven methods that have helped us work better as a design team, which we have also used to optimize the design practice for our clients. In this section, we will walk through the steps we take to implement DesignOps, and provide additional insight into some common problems we see within organizations that your business may be struggling with as well.

Step 1: Assess current state and identify pain points

In order to best implement DesignOps for our clients, our process starts with developing a more thorough understanding of where the organization’s design practice is at today. Similarly to how we solve UI design problems, we typically start these projects conducting research to better understand the current state and identify the largest pain points. This can save your organization time by avoiding focusing on the wrong things, and instead utilizing your time and energy addressing the specific aspects that will make the most impact for your team and your business.

To identify what problems DesignOps can best address, you first should conduct research into the make-up of your design team, what their process looks like when doing research and design work, and how your designers are collaborating and supporting other teams within the organization. At Fuzzy Math, we help organizations conduct this research through a series of assessments. We gather information from UX leaders, contributors, and other teams within the organization to better understand the current state. These assessments can help uncover inefficiencies and inconsistencies within our client’s design process and misalignment within their design team and across the full organization as it relates to the purpose of design. Fuzzy Math asks organizations a variety of questions to assess an organization’s design practice as it relates to these three key areas:

• People: The design team has an intention that drives their work and propels them forward.
• Purpose: The design team feels their purpose is known and valued within the organization
• Process: A user-centered design process is embedded in the work that’s produced and delivered by the design team.

Step 2: Uncover solutions and take action

Once you have uncovered the key problem areas that may be leading to inefficiencies and misalignment within your design team, you can take action in implementing DesignOps to address these issues head-on. Here are a few examples of common problems we typically see with the clients we work with that your organization may be running into as well, including specific actions your company can take to implement DesignOps to address those issues:

Designers are siloed and producing inconsistent, lower quality work

Especially for larger organizations where designers may be working on separate workstreams without much overlap, it can be hard to ensure consistency, and for designers to all be aware of previous design decisions. This can lead to a higher risk of designers producing work that isn’t aligned with the product vision, that needs to be redone, and that may not provide the best user experience.

Creating and maintaining a design system is essential in helping to keep all designs for a product consistent. It also can reduce time wasted looking for specific design assets in old documentation, or redesigning something that was already designed. Fuzzy Math recently created a design system template to help us in our own design process which we use to more efficiently create design systems for our clients to ensure successful implementation and scalability.

Other documentation and standardized training can also help address this issue. This can include setting up training and utilization requirements for common tools, like Figma, to ensure designers are working efficiently, and in a way that supports consistent integration across different projects. As a result, designs don’t just look the same, but are built in ways that the entire team understands and can utilize for future iterations of your product.

Lastly, scheduling collaboration and feedback sessions that bring designers together across teams can provide opportunities to share work, learn from one another, and ensure design decisions for all offerings from a business are aligned. At Fuzzy Math, we implement a monthly meeting called a “Designer Hangout”, where all designers across multiple projects are invited to share what they have recently learned on projects, showcase their work, and receive feedback from other designers on our team. These opportunities also helps make design teams feel more connected, especially when designers may be currently siloed and focused on different workstreams or projects.

UX design isn’t well understood throughout your organization

When the value of design is not well communicated throughout your organization, it is harder for design to be implemented during the right times and in the most impactful way.

Crafting a mission statement for your design team can both ensure your designers have a shared purpose, but also can communicate that purpose to other teams and leaders. A mission statement should align with your larger business goals, and feel connected to its success. Organizations also should provide opportunities for designers to educate others about the user-centered design process to help it feel better integrated into the overall culture. This helps to ensure all decisions are being made with the user in mind, and can help maximize impact and customer or client satisfaction.

Another step to communicate the value of design is to create metrics to measure it. Establishing KPIs related to design outputs provides ways to track the impact of design as it relates to your business’s bottom line. KPIs should measure aspects important to your organization’s success including time to market for a product, user retention, and usability.

As your larger organization better understands the design process and its measurable impact, design will be better integrated and enabled to support the success of other teams such as development, marketing, and product management.

Designers are burnt out, unsatisfied, and motivated to leave

In order to retain top talent, organizations need to support their designers and ensure they have opportunities to provide value.

Having a process around resourcing designers on projects, and ensuring you have a team that can support requests and scale as your company grows is essential in preventing designers from being overworked. This includes evaluating the ratio of developers to designers, ensuring the design team is big enough to handle the work that is trying to be developed without causing a bottleneck.

Setting clear processes for approval and feedback also helps to avoid frustration from unclear timelines, drawn out iteration cycles, or confusion when there is conflicting feedback coming from too many directions without a clear approver.

Additionally, designers should feel like they have ownership over their designs, and have space to contribute to the strategic design direction. To avoid having them feel like “pixel pushers”, ensure design is being implemented at the right times and integrated into the overall vision for your products or services. This includes creating processes for user-centered research through the establishment of ResearchOps, so designers have the time and resources to identify pain points and align design decisions to real user needs.

When design feels like an important, well-integrated aspect to the business’s success and is given the proper resources and support, designers will feel more respected and valued thus leading to increased job satisfaction and reduced turnover.

Step 3: Measure impact

Whatever actions your organization needs to take to implement DesignOps, it is critical to ensure that you are also setting up metrics to measure its success, and the impact those changes have on your design team and the business. A few examples of metrics include:

• Design team retention rates and overall satisfaction scores
  • Does your design team feel more fulfilled and invested?
  • Are they more likely to stay?
• Design team performance and efficiency
  • How long does it take for designers to do their work?
  • Are they performing successfully and in alignment with their role?
• User satisfaction score, net promoter scores and quantitative tracking
  • How satisfied are your customers with your company?
  • How satisfied are your customers with your product specifically?
  • Are users able to utilize the product successfully?

When setting up metrics, be realistic about what metrics make the most sense to track for your organization and ensure you can track those metrics regularly over long periods of time to get an accurate sense of any measurable changes.

Conclusion

Design Operations is the key to optimizing your design practice within your organization. Through the implementation of DesignOps, your design team can maximize their impact and mitigate risk through increased efficiency, standardization, and an aligned purpose. At Fuzzy Math, DesignOps has helped us as a UX design team work more efficiently across all projects, train and retain our designers, and create better solutions for our clients.

Does your organization need help getting the most out of your UX team? Fuzzy Math has been refining our own DesignOps and that of our clients since we were founded in 2009. Get in touch to see how Fuzzy Math can help implement DesignOps within your business.

The post DesignOps – What is it, and why your design team needs it appeared first on Fuzzy Math.

Updated April 2026:

I now use AI Tools consistently, so that’s an update. I use Chat GPT, Claude, Midjourney, and some of the built-in AI features in tools I was already using (Figma, Notion, Photoshop, Replit). I’m intrigued by Claude Code and interested in the way both developers/non-developers could be using it. I think there’s value in designers skipping the prototyping step and going straight to code.

I am concerned, though, maybe even more than I was initially. Back in 2023 it was all speculation; now we’re seeing the real-world implications it has on the job market (not to mention the environment).

Overall, learning/using the tools has become a no-brainer for me, and I genuinely enjoy the process of collaborating back and forth with AI. But the fears/consequences are valid, and they remain in the back of my mind every time I open Claude.

Original Post:

For someone who works in tech, I would not consider myself super tech-savvy. I’m a slow typer, I don’t use too many keyboard shortcuts, and I jot down notes in a physical notebook. By the time I figured out my favorite way to build components in Figma, they released Variables into the ring, and my entire game was thrown off (don’t get me started on how long it took me to understand Auto Layout).

In that case, it’s probably no surprise that I have yet to introduce AI into my workflow.

I stumbled upon this tweet by engineer Santiago Valdarrama in a Medium article scroll. I found myself appropriately unsettled considering what I just told you about myself, but Valdarrama is right: AI tools will be the new standard in any given design process. The sooner we become comfortable with these tools, the better off we will be. 

This might sound daunting if you’re anything like me, someone slow to fully adapt to new technologies. Luckily for us, I have colleagues here at Fuzzy Math who keep up on all the latest technology trends—at the very least, they’re quicker than I am to test out different tools. These designers are not scared of AI the way I am: one has already written about it extensively in Embracing AI in Design: How Designers and AI can Collaborate. If you haven’t already, read Tré’s article for an in-depth overview of AI and for strategies designers can use to adapt to the new world. Otherwise, read on for a round table discussion about AI tools such as ChatGPT, Grammarly, and Notion, as well as the ways in which my coworkers are already integrating these tools into their everyday workflows.

*Note: In a few instances during the round table, we use “automation” and “AI” interchangeably. I want to note here the difference between the two: automation relies on a set of rules that were predetermined, while AI can learn and make its own decisions based on data and new information (similar to the way a human makes decisions). Here is a great article by Maria Homann to learn more about that distinction.

FM Round Table on AI

The post AI & FM: Integrating AI Into Your Workflow appeared first on Fuzzy Math.

It’s true that we’re not all data security engineers, the people whose job it is to ensure a company’s data is protected from potential threats. But security is an increasingly vital facet of product strategies in all industries. When every tap, click, and swipe leaves behind a digital footprint — a treasure trove of information from personal identifiers to sensitive financial details — the challenge is often in balancing user needs and convenience with additional security measures. 

Today, we’ll dive together into the intricacies of data security, unraveling the challenges that designers encounter on this path and why considering data security isn’t just a checkbox on the to-do list. 

Why is designing for data security important?

Incorporating data security into UX design is not just an added layer of protection; it’s an integral part of a successful business strategy. Failing to prioritize data security can lead to breaches, legal consequences, loss of user trust, and significant damage to an organization’s reputation. UX designers must collaborate closely with security experts and follow best practices to safeguard user data from the outset of a project.

Consider a few reasons why designing for data security is critically important:

Protection of User Data

UX designers handle a wealth of user data, including personal information, login credentials, and potentially sensitive financial or health-related data. Ensuring the security of this information is not only a legal and ethical obligation but also essential for maintaining user trust.

User Trust and Confidence

Speaking of user trust, users are more likely to trust and engage with a product or service that demonstrates a commitment to data security. A secure UX fosters trust, which is a vital component of user satisfaction and loyalty. In fact, trust is one of the key measures of product success, and one that we often look at when using metrics like SUPR-Q. 

Legal and Regulatory Compliance

Numerous data protection regulations, such as GDPR (General Data Protection Regulation) in Europe or HIPAA (Health Insurance Portability and Accountability Act) in healthcare, mandate strict data security practices. Other industries like finance, HR and recruitment, telecoms, and higher education, just to name a few, also cite data security as a critical concern and may have their own unique regulations to consider. Non-compliance can result in severe penalties and reputational damage for the organization, so ensuring that the user interface and user experience comply with data privacy regulations is paramount.

The Challenges of Designing for Data Security

While designing for data security is crucial in any industry, designing data security products often presents a unique set of challenges due to the sensitive and complex nature of the domain. These challenges often revolve around balancing security requirements, usability, and user trust. 

See how we applied our UI/UX design process to solve the challenges of redesigning a legacy data security product. Data Security & Risk Management Platform Case Study

Complexity of Security Concepts

Data security involves intricate technical concepts and terminology. Designers must find ways to make these concepts understandable to a broad audience, including non-technical users and executives.

User Education

Many users may not fully understand the risks and best practices related to data security. Designers need to create intuitive interfaces that educate users about security threats and guide them on how to mitigate risks.

Contextual guidance is one technique in a designer’s toolbelt to ensure that users can find the help that they need no matter where they are in the process. By layering in help and FAQs throughout the interface, we can make it easier for users to find answers to the questions that they have when they have them. 

In enterprise and B2B tools, though, designers must also contend with designing for both novices and experts. Finding the right way to build up to complexity so that the educational resources and additional help don’t get in the way of expert users can be a challenge, especially in complex and technical industries such as data security. 

Balancing Security and Usability

Striking the right balance between robust security measures and a user-friendly experience is challenging. Implementing stringent security protocols can sometimes lead to cumbersome user experiences, while prioritizing usability may compromise security. It’s important to strike the right balance — and to verify the success (or failure) of that balance through usability and validation testing with the right set of users.

Multi-Platform and Device Considerations

Data security tools often need to work across a variety of platforms and devices, including desktops, mobile devices, and IoT devices. Designing for consistency and security across these platforms can be challenging.

Understanding not only the why, but also the how and the who, is crucial to designing for multiple platforms.  During research, be sure to consult with users from different departments to gain a more holistic understanding of all your users’ needs. For example, big touch targets, CTAs, and text fields may be necessary in an environment where timely decisions are made and recorded quickly. A user who spends their days on a desktop computer, on the other hand, may benefit more from a design that allows them to consume more relevant information at once.

Incident Response and Reporting

Designing interfaces that facilitate the reporting of security incidents and guiding users through incident response procedures is another challenge to designing security products. When designing complex workflows, designers often start by mapping out the process with process flows and diagrams to ensure that they are thinking holistically about the entire workflow. These deliverables also help to establish that the whole team (including product owners, stakeholders, and developers) is aligned on the steps and data associated with the process. Starting with process flows helps teams make decisions earlier and faster, allowing designers to spend time in the details rather than on reworking the process.

Customization and Configuration

Many data security solutions require extensive customization and configuration to meet an organization’s specific needs. Designing interfaces that allow users to configure security policies and settings without overwhelming them with options is a challenge.

For B2B and SaaS products, it’s nearly impossible to design a one-size-fits-all solution. And although customization is important, we often find users have a hard time knowing where to start. Presenting them with a blank page, with a world full of possibilities, can lead to indecision, fatigue, and task abandonment. One strategy to combat this challenge is to design templates that can either be defaulted or recommended to the user. In an ideal world, users should then be able to customize their preferences from there based on their unique organizational needs. 

Integration with Existing Systems

Similarly, ensuring that the security tools seamlessly integrate with an organization’s existing IT infrastructure and software applications can be technically challenging. 

In enterprise products, one of our first steps is to dive deep into understanding a company’s technological ecosystem before starting any design work. Of course, for B2B and SaaS products, this ecosystem can look vastly different at each end user’s organization — again, necessitating well-designed and flexible customization patterns.

Scalability

As organizations grow, their data security needs evolve. Designing interfaces that can scale with an organization’s growth is a challenge. A good framework is crucial, as is designing with scalability in mind. 

Designing for a data security company requires a deep understanding of both the technical aspects of security and the human factors involved. It involves a constant balance between security, usability, and compliance, making it a unique and demanding field in the realm of user experience design.

The post The Challenges of Designing for Data Security appeared first on Fuzzy Math.

Lack of clarity, alignment, and communication have caused the team to once again end up in the hapless place where initiatives stall, projects languish in limbo, and the dream of a shared vision feels alarmingly out of reach. Feedback has been coming at the project from all directions: comments, stickies, and random written text scatter across your team’s shared canvases of online collaborative platforms, leaving everyone bewildered.

Maybe you’re nodding your head in agreement? Maybe you’ve come to the right place.

In this blog post, we’ll explore the fundamental role storytelling through UX storyboarding can play in product strategy discussions, and how it can serve as both an internal consensus building tool within organizations and as a means to share a grander vision that bridges departmental silos.

Writer’s Note: Before you get lost amid a sea of tabs and scattered pursuits  – this is my debut blog post. The first thing I’ve chosen to write about is essentially how to keep someone’s attention. So, humor me for a moment and see how I do?

The Power of Storytelling through UX Storyboarding

In the ever-evolving landscape of strategic product development, where ideas and ‘what-ifs’ bounce around freely and priorities often compete for attention, two ancient tools remain secret weapons, allowing people of diverse backgrounds to come together: storytelling and storyboarding.

Storytelling is in Our DNA

From ancestral cave paintings to the mischievous tales of “Calvin & Hobbes,” storytelling has been an essential part of human communication since the beginning of time. And while we may not be carving hieroglyphics on stone walls or weaving tales around a campfire like our ascendent, the essence of these age-old practices remains as relevant as ever.

At the heart of storytelling lies the ability to transport your audience into a world not yet realized. It’s about enabling others to visualize not only what the possibilities of the future can look like, but also what the complexities and frustrations of the present may look like by painting an innovative, yet tangible idea through spoken words, written stories, and visual illustrations.

Nevertheless, even the most eloquent storyteller, armed with a rich vocabulary and a knack for weaving language into concrete narratives, can come up short while struggling to find the right words to truly unveil the value of the stories being told – especially when it involves conveying design ideas about ‘what-ifs’ and ‘could-bes’, which are inherently conceptual.

Design, by its very nature, is elusive when expressed solely in words.

Words Alone Fall Short

In the realm of product design, whether it’s a groundbreaking product roadmap or the intricate details of a project phase, words alone often abstain. That’s partially due to the fact that eloquent and effective delivery of product design concepts requires the individual to adequately capture an entire journey from conception to execution. More importantly, every decision – no matter how minute – can have a profound impact on the end result. But design also exists in a territory where individual perspectives on what is essential can wildly diverge. Sometimes this often leads to misunderstandings and misalignment. That is why it’s imperative to effectively capture ideas and frequently gather feedback from highly invested stakeholders and subject-matter-experts. 

Let’s consider a scenario where you’re faced with a critical decision in product development but the team is divided, each member passionately advocating for their own vision, fueled by their own priorities and perspectives. You need alignment, a shared vision, and a way to bridge the gap between any competing ideas. Decisions need to be made swiftly and confidently, but everyone seems to always enter meetings ready to defend their “hill to die on” when it comes to certain design features.

But, let’s face it – none of this should come as a shock. There has never been a universal design language that magically bridges the gap of understanding when discussing design decisions. Engaging in conversations about product features with cross-functional teams only deepens this struggle, as not everyone shares a common foundation of understanding.

Moreover, teams have grown weary of the tedious discussion cycles around painstakingly text-heavy slide decks that list product requirements and acceptance criteria – a process that often feels like you’re revisiting the same, eerily similar discussions from past stalled product initiatives.

But in reality, the issue isn’t a lack of enthusiasm or a shortage of good ideas. It’s the sheer volume of information, the nuances of effective communication, and the scarcity of time.

This is where UX storyboarding becomes the unifying force.

UX storyboarding can serve as the missing link that fosters a more universal language, which reduces the risk of misinterpretation and misdirection from all team members. It creates a shared visual glossary that team members can reference continuously throughout a project to ensure that everyone is on the same page when discussing design elements. It simplifies complex ideas and fosters a common understanding, smoothing the path toward consensus.

But before we dive into understanding how the combination of storytelling and UX storyboarding can facilitate more effective project sign-offs, let’s quickly summarize some storyboard basics.

What is Storyboarding?

By definition, a storyboard communicates a story through a series of images displayed in a sequence of panels that chronologically map out the story’s main events.

Storyboarding has a rich history that spans a multiple of industries, from film and animation to advertising and product development. Early pioneers – like Winsor McCay and Walt Disney – recognized the value in planning animated sequences, which led to storyboarding’s establishment as a standard practice in film and animation. Come the mid-20th century, the advertising and design industries adopted storyboarding as a means to more effectively pitch ideas to clients.

Today, the level of fidelity in storyboarding can differ across industries based on a slew of needs. But at its core, storyboarding provides simple visuals and basic, but memorable scenarios that are simpler to understand at first glance and easy to retain. Storyboards often share three common elements that create the inexhaustible structure for a rich storytelling experience.

• Specific Scenario: First, storyboards describe a specific scenario or user story. The persona that corresponds to the scenario is clearly specified at the top of the storyboard, paired with a short text description that explains the logical flow of information and tasks. It should be clear enough that a team member or stakeholder could understand what is depicted before looking at the visuals.
• Visuals: Second, each storyboard scenario should be represented through sequential visuals. These can be sketches, illustrations, or photos. Depending on the purpose of the storyboard and its audience, these visuals can be quick, low-fidelity drawings or elaborate, high-fidelity artifacts. Visuals should include details relevant to the story, such as the user’s environment, speech bubbles with user quotes, or sketches of the screen that the user is interacting with.
• Corresponding Captions: Lastly, each visual should have a corresponding caption. The caption describes the user’s actions, environment, emotional state, device and so on. Because the description and visuals provide the primary content for a storyboard, corresponding captions should be concise and don’t typically need to exceed more than two bullets.

Okay, so storyboarding seems simple enough – let’s get back to business!

UX Storyboarding as an Internal Sales Tool

When you’re vying for project sign-offs or consensus building, it’s not enough to rely solely on spreadsheets and email correspondence. I feel like it’s pretty safe to say that all of your team members are likely dealing with juggling multiple priorities, competing interests, and ever-evolving schedules. Simply put, you need a way to captivate your audience and inspire them to believe in your vision.

User-centered storyboarding allows you to package your ideas in a compelling narrative, making it easier to garner buy-in from your team. This powerful tool can be the key to unlocking project sign-offs and fostering alignment across departments, which is essential in a fast-paced business environment.

The Benefits of (Story) Boarding!

Improved Communication

When conveying design ideas to stakeholders, team members, or to clients who may not have technical or design backgrounds, storyboards provide a clear and easily digestible medium for people of diverse backgrounds. Visual storytelling in storyboards often surpasses written or verbal explanations, ensuring everyone is on the same page.

Early Problem Identification

Storyboards are proactive problem-solvers. By visualizing the user journey early in the design process, coupled with intentional and proactive discussions, they help to uncover potential flaws, bottlenecks, or usability issues. This foresight allows necessary adjustments to be made before the development phase, saving time and resources. This rapid, iterative process can help lead to the identification of potential issues or improvements early in the design process.

By visualizing and testing ideas early, by making more informed choices, and by reducing the likelihood of costly design changes after development has begun, storyboarding helps to reduce the risks associated with design decisions.

Storyboarding allows for the exploration of multiple design ideas and scenarios in a low-cost and low-risk manner. This rapid iteration can lead to the identification of potential issues or improvements early in the design process, reducing the need for costly changes later in development.

Enhanced Collaboration and Decision Support

Storyboards facilitate collaboration between you, the designers, and other stakeholders. They provide a common visual language that fosters better teamwork and idea sharing, which ensures that all parties are aligned on the design direction and objectives.

Storyboards serve as a foundation for discussions and decisions. You can use them to evaluate different design options, to make informed choices, and to prioritize features or interactions based on their impact on the user’s journey.

For those seeking investment or funding, a well-crafted storyboard can be a persuasive tool. It can demonstrate a clear vision and a thoughtful approach to the user experience, which makes your project more appealing to potential investors and partners.

A Note on Empathy

It’s important to note that storyboarding only leads to productive conversations around the prioritization of efforts if the user scenarios truly reflect users’ behaviors. This also assumes that the creator didn’t pick certain visualizations or outcomes just for the sake of the storyline.

In other words, if you ultimately want a storyboard that enables others to step directly into the user’s shoes, to trace their ideal path through the product, and to pinpoint potential pain points and areas ripe for improvement, then you’ll need to invest the time in appropriately adopting the user’s perspective. This requires a deeper examination of users’ needs, behaviors, characteristics, and context of use. With a more holistic understanding of the user, you can more easily craft a narrative that illustrates your strategy and allows your team to see the user’s journey from start to finish.

The key to creating a cohesive and compelling storyboard is to identify the sweet spot where business strategy, project goals, and user behaviors intersect – an intentional navigating of the human mind, some may say – which, lucky for you, dear reader, happens to be exactly what we specialize in.

Maximizing Storyboarding with UX Design

Effectively communicating product design isn’t just about aesthetics and functionality, it’s about conveying emotions. Storyboarding can be a valuable tool to ensure the design process remains focused on providing a seamless and satisfying user experience.

At Fuzzy Math, our user-centered design process is carefully constructed to enhance the quality and impact of storytelling through UX storyboarding. In this section, we’ll explore how activities laid out within our design process can facilitate more cohesive and representative storyboard scenarios to support your product strategy.

Kickoff and Design Principles

Set the stage for effective storyboarding by working with our team to establish design principles and define project goals for your platform in a kickoff workshop. With your team, you should plan to answer questions like, “How do you want your users to feel while using the platform?” and “How do you want your designs to be perceived?” By aligning storyboarding methods with intentional design principles, you can ensure that the visual narrative remains consistent with your desired user experience.

Already want to get started? Dive into the Design Thinking Process now, or get in touch.

Stakeholder Interviews and Ecosystem Map

Meet with our team in stakeholder interviews to ensure we have a foundational understanding of the key business goals and drivers related to your product. Describe the context in which your product lives or will live and lay out these details in an ecosystem map. Depending on the project, this may include people, organizations, systems, locations, and any other entity useful to understand the product environment. This activity can give everyone a visual representation of all the factors at play within the context of the product’s environment and how they all relate to one another.

User Personas and Scenarios

Collaborate with our team to clarify your target users and map out their experience with your platform. Define specific user scenarios or use cases that are representative of your target personas. Highlight emotional aspects of the journey, indicating moments of satisfaction, frustration or enthusiasm.

Journey Maps

Understand where and how users interact with your product to help establish user journey maps that outline the steps needed for users to achieve their goals within your product or service. Identify features or interactions that streamline tasks and reduce user efforts.

Storyboards should depict a clear and logical flow of information and tasks. As part of our process, we conduct a User Journey Workshop to help define appropriate user personas and a user journey map. This helps to ensure that the sequence of frames included in the storyboard represent an intuitive user journey that highlights how information is organized, categorized and presented within the product.

Learn more about FM’s take on how Journey Mapping is the Key to Digital Transformation!

Competitive Analysis

Dive into a competitive analysis of your business landscape to identify insights into industry benchmarks and user expectations.

Interaction Concepting

Participate in interaction concepting workshops that yield feature prioritization discussions and UI interface sketches. This will help bring the narrative to life once we translate these concepts into key page UI designs that will serve as the visual backbones of your storyboard.

Key Page UI Design and Wireframing

Help to define specific scenes and descriptions, which, at Fuzzy Math, we bring to life through key UI designs imagined through wireframes, which will serve as the visual backbone of our storyboards.

Storyboards

Share your storyboards with stakeholders, team members and potential users to gather feedback and ensure their effectiveness.

Have you ever thought that communicating your design decisions to stakeholders feels a little bit like you’ve stepped out of your designer shoes and into the role of a salesperson? Well, you’re not alone! Listen to Fuzzy Math’s design leadership podcast today, and hear about the importance of stakeholder management with Amazon’s Nate Felt. UX Leadership by Design – Episode 4: The Importance of Stakeholder Management

Storyboards breathe life into the user experience, vividly illustrating entire user journeys or specific interactions within a digital product or service. With a storyboard in hand, any stakeholder can step into the user’s shoes, and can trace their path back through the product.

A well-designed user experience, as depicted in a storyboard, can lead to higher user engagement and satisfaction. That translates to better user retention, to increased sales, and to a more successful end product.

This is where the art of UX storyboarding shines, offering a strategic tool that empowers designers, stakeholders, product teams, and many others to focus on what truly matters: the user. User-centered storyboarding goes beyond the surface, diving deeper into the user’s journey. It serves as a visual representation of not only the ‘what’ but also the ‘why’ behind design choices.

Final Thoughts

Storyboarding in UX design is an invaluable tool for all types of clients. User-centered storyboarding helps you understand, communicate, and refine your design ideas. This process ensures your final product meets user needs, reduces design risks, enhances collaboration and decision-making, and leads to a more successful and user-friendly outcome. It’s an essential step in the journey towards creating a product that truly resonates with your audience.

Discover how Fuzzy Math can make your business strategies come to life and get in touch today!

References

1. https://www.nngroup.com/articles/ux-stories/
2. https://www.nngroup.com/articles/storyboards-visualize-ideas/

The post UX Storyboarding as a Unifying Force appeared first on Fuzzy Math.

I’ll say it – I had trouble when I was a new designer. I wasn’t a unicorn, or a manticore, or any other tech-industry beast capable of bringing my designs to perfectly coded front-end fruition all by myself. Instead, I was a (relatively) fresh minted bootcamp graduate and a newly hired UX designer at Fuzzy Math. Even though Fuzzy Math has a great onboarding team and program for new hires, I was still unsure of my Figma-footing and all of my design decisions when I dove into my first client project here. 

I feel that I’ve grown a lot since then (obligatory ‘I still have more to grow’ here) and I owe so much of that growth to the exemplary design leads at Fuzzy Math. Knowing they were there on every project, heads down in design files with me to serve as a source of guidance, design truth, and vision allowed me to grow far faster than I would have if I had been hired somewhere with a less robust team structure or the dreaded ‘Design Team of One’. 

So, the design leads at Fuzzy Math are an integral part of our ability to provide great designs to our clients. But that’s nothing new, right? It’s not exactly a scalding hot take to say that good leadership helps produce good results. I know this. But what I’d like to do in this article is dive deeper into the Fuzzy Math structure, our ‘ecosystem’, and explore not only why design leadership here produces great results, but also how our great design leadership and team structure contribute to the creation of new design leads to usher in the next crop of new designers.

Enter Madeleine Byrne

Who is Madeleine Byrne?

Madeleine is my coworker, a fellow designer, and an enjoyer of baking and textiles. She is also, more importantly (for this article) Fuzzy Math’s newest design lead. 

I want to take a look at Madeleine’s journey through the ‘Fuzzy Math ecosystem’; from FM design intern to FM design lead. While not everyone at FM takes the exact same route that she took to get to where she is now – I do think that her path is indicative of how the environment at FM can help people grow and in return help others grow. It’s an indicator that something is going right, which is fun for me to explore because in my blog posts I often focus on things that are going wrong. 

In addition, Madeleine has gone through almost every single part of the aforementioned ‘Fuzzy Math ecosystem’ – Internship, UX and Visual Designer, Internship Lead, and Design Lead – which allows us to take a look through her journey to better explore all the moving parts that help make FM special.

Starting from the beginning – 

The post The Fuzzy Math ‘Ecosystem’: Nurturing Design Leadership appeared first on Fuzzy Math.