Co-design sessions are a valuable tool for companies looking to develop new products or services, or to improve existing ones. By bringing together a diverse group of stakeholders, co-design sessions allow you to explore and understand the needs and challenges of your target audience, and to design solutions that are tailored to those needs.
Let's talk
Improved user experienceBy centering your target audience in the design process and involving them in the validation process, you can create products and services that are more intuitive, user-friendly, and effective. This can lead to improved customer satisfaction and loyalty.
Increased innovationCo-design sessions allow you to explore a wide range of ideas and perspectives, which can lead to more innovative and creative solutions. This can help you stay ahead of the competition and drive business growth.
Cost savings from less reworkBy involving your target audience in the design process, you can reduce the risk of developing products or services that don't meet the needs of your customers. This can ultimately lead to cost savings, as you are less likely to have to go back and make significant changes after the fact.
Greater buy-inBy involving stakeholders in the design process, you can build consensus and buy-in for your products and services. This can help to ensure their success and adoption within your organization.
By partnering with us for co-design sessions, you can tap into the benefits of a collaborative, user-centered design process and create products and services that are more innovative, effective, and successful.
At This Dot Labs, we facilitate and participate in co-design sessions to help our clients create innovative and effective products and services. Our co-design process is designed to be collaborative, participatory, and user-centered, and includes the following steps:
We work with you to define the problem or challenge that you are trying to solve, and to identify the key stakeholders who will be involved in the co-design process.
We facilitate a collaborative ideation process to generate a range of potential solutions. We get around a big digital canvas and everyone starts brainstorming and evolving ideas.
We use a variety of methods to validate designs with stakeholders, including user research, focus groups, and interviews. We create clickable prototypes and/or proof of concept implementations to facilitate this testing. This helps us to validate the assumptions and decisions made in the designs against the needs, challenges, and opportunities of your target audience, without spending too much on product development.
Based on the results of testing, we help you to refine and iterate on your prototypes to create a final product or service that meets the needs of your target audience. By partnering with us for co-design sessions, you can be confident that you have a team that is skilled in facilitating collaborative and user-centered design processes. Our co-design sessions are an effective way to ensure that your products and services are tailored to the needs of your target audience, and are more likely to be successful in the market.
Optionally, we can expand on the assessment engagement to turn the prototypes into a full design system or work alongside your team to implement the designs.
Our clients are building for the future. Explore This Dot Labs' portfolio, and see how we have helped them achieve their diverse technical goals.
topics covered in this case study:
Supported by a Chainlink Community Grant, This Dot Labs recently created Smart Contract Database (DB), an open-source website for the Chainlink developer ecosystem.
topics covered in this case study:
In collaboration with Chainlink Labs, This Dot Labs both designed and developed the Ecosystem Map application with the goal of delivering a product that could scale to feature a large number of resources while remaining simple to navigate, fully responsive, and accessible.
topics covered in this case study:
The client, a supply chain technology solutions provider, offers a freight management platform that helps companies and customers manage the quality and accuracy of shipments with greater ease.
topics covered in this case study:
The team behind the Google HTML-based web development framework, Accelerated Mobile Pages (AMP), approached This Dot Labs for an educational strategy and resources. Our team provided an array of developer experience and advocacy services to help attract and empower new users.
We're ready to be your trusted technical partners in your digital innovation journey.
Whether it's modernization or custom software solutions, our team of experts can guide you through best practices and how to build scalable, performant software that lasts.
Discover how adopting a scientific mindset can transform your software engineering practice....
Jan 10, 2025
14 mins
Explore writing SQL queries using the D1 client library and its trade-offs vs ORM’s...
Dec 23, 2024
6 mins
I recently participated in an audio space with the Stripe team, and something they said really stuck with me: the Stripe app store is a growing area that isn't overly saturated yet....
Dec 18, 2024
4 mins
Svelte 5 was finally released after a long time in development. Fortunately, we've been able to test it for some time, and now it has a stable release....
Nov 27, 2024
4 mins
As web developers, we're often working with external data that we don’t control and can’t expect to meet our expectations. But with the Zod library, we can define expected data schemas and validate incoming data against them....
Nov 15, 2024
7 mins
Understanding the Difference Between :focus and :focus-visible in CSS I have learned my fair share about the importance of keyboard accessibility, so I know that visual indication of the focused element is very important. But the well-known :focus pseudo-class is not always the best fit for this job. That's where :focus-visible comes in. Let's look at the differences between these two pseudo-classes and explore the best practices for using them effectively. What is the :focus Pseudo-Class? The :focus pseudo-class is a CSS selector that applies styles to any element that receives focus, regardless of how that focus was triggered. This includes focus events from keyboard navigation, mouse clicks, and touch interactions. Example Usage of :focus ` In this example, the button will display a blue outline whenever it is focused, whether the user clicks on it with a mouse, taps it on a touchscreen, or navigates to it using the keyboard. What is the :focus-visible Pseudo-Class? The :focus-visible pseudo-class is more specialized. It only applies styles to an element when the browser determines that the focus should be visible. This typically occurs when the user navigates via the keyboard or assistive technologies rather than through mouse or touch input. Example Usage of :focus-visible ` Here, the button will only show a blue outline when focused through keyboard navigation or another input method that usually requires visible focus indicators. Key Differences Between :focus and :focus-visible :focus - Behavior: Applies to any element that receives focus, regardless of the input method. - Use Cases: Ensures that all interactions with the element are visually indicated, whether by mouse, keyboard, or touch. :focus-visible - Behavior: Applies styles only when the focus should be visible, such as using a keyboard or assistive technology. - Use Cases: Ideal for scenarios where you want to provide focus indicators only to keyboard and assistive technology users while avoiding unnecessary outlines for mouse and touch users, typically required by design. Accessibility Implications :focus - Pros: - Guarantees that all users can see when an element is focused, which is critical for accessibility. - Cons: - Can lead to a suboptimal experience for mouse users, as focus styles may appear unnecessarily during mouse interactions. :focus-visible - Pros: - Enhances user experience by showing focus indicators only when necessary, thus keeping the interface clean for mouse and touch users. - Tailors the experience for keyboard and assistive technology users, providing them with clear visual cues. - Cons: - Additional considerations may be required to ensure that focus indicators are not accidentally omitted, especially in older browsers that do not support :focus-visible. - There may be cases where you want to show focus indicators for all users, regardless of input method. Best Practices for Using :focus and :focus-visible To achieve the best accessibility and user experience, combining both :focus and :focus-visible in your CSS is often a good idea. Combining :focus and :focus-visible ` Here is a Stackblitz example of what such styling could look like for you to try out and play with. Additional Tips - Test with Keyboard and Assistive Technology: Ensure that your web application is navigable using a keyboard (Tab, Shift + Tab, etc.) and that focus indicators are visible for those who rely on them. It's never a bad idea to include accessibility testing in your e2e testing suite. - Provide Clear Focus Indicators: Make sure that focus indicators are prominent and easy to see. A subtle or hard-to-spot focus indicator can severely impact accessibility for users who rely on keyboard navigation. Conclusion The :focus-visible pseudo-class offers a more refined way to manage focus indicators, improving accessibility and user experience, particularly for keyboard and assistive technology users. By understanding the differences between :focus and :focus-visible, and applying best practices in your CSS, you can create more accessible and user-friendly web applications. Remember, accessibility should never be an afterthought. By thoughtfully applying focus styles, you ensure that all users, regardless of how they interact with your site, can easily navigate and interact....
Nov 8, 2024
3 mins