Requirements gathering
- Elicitation of user needs
- Discovery of business goals
- User and stakeholder interviews and workshops
- User observation
- Persona development
- User story development
Breadcrumb Digital has extensive experience in designing and developing digital products.
We focus on user adoption and apply best practice user experience (UX) principles to deliver solutions people want to use and champion.
‘Good enough’ is no longer acceptable. Well-designed online products are part of everyday life, and our collective expectations have never been higher.
But that’s not the only reason to invest in UX. Good UX design reduces development waste and means fewer support calls post-launch.
An estimated 50 per cent of development time is spent on re-work that could have been avoided with more focus on defining and refining the UX.
Our introductory UX reviews map primary user tasks against current system functionality to see where features already line up and where there is room for improvement.
“Could this be easier?” and “What would users do?” are the driving questions that guide a product review, examining aspects such as content style and organisation, formatting, navigation, responsiveness, interactivity, and accessibility.
We provide written reports with specific references to any elements or issues, including screenshots where appropriate. These reports also contain high-level recommendations and outline next steps so it’s easy to get started on making improvements.
From designing a new system to redeveloping an existing one, we provide UX support for in-house teams, projects where Breadcrumb is the primary vendor and projects where Breadcrumb supplements the skills of the primary vendor.
Our UX methodology relies heavily on engaging with users and business stakeholders while collaborating with the project team and developers. These engagements include:
We also implement working prototypes as quickly as possible to gather user and stakeholder feedback.
Where possible, we prefer to take an iterative approach to our UX projects. We do this because: