Written scope and responsibilities
We document deliverables, responsibilities, dependencies, review points and exclusions before production begins, so every participant works from the same agreed scope.
User Experience & Interface Design
UX/UI Design for Clearer Product Decisions
We test structure, flows and interactions against real evidence before polishing the interface.
NovaCraft maps user journeys, prototypes critical flows, reviews evidence and documents interface behaviour so development starts from clearer product decisions.
- Research & Flows
- Wireframes & Prototypes
- Design Systems
- UX research and audits
- User flows and journey mapping
- Information architecture
- Wireframing
- Interactive prototypes
- Interface and visual design
- Design systems
- Usability testing
- Accessibility review
- Developer handover
What we can do
UX/UI Design Scope
A new product needs different work from one with existing users and existing data. We agree which of these your project actually needs before quoting it.
We work through your existing product as a user would, note where journeys break down, and give you a prioritised list of what to fix and in what.
Stakeholder interviews, competitor review and, where you have them, conversations with real users, so design decisions rest on something firmer than opinion.
We organise content, navigation and labelling so people can predict where things live instead of hunting for them.
Low-fidelity layouts that settle structure, hierarchy and sequence while changes are still cheap to make.
High-fidelity screens built on your brand, with states, empty views and error cases designed rather than left for the build to invent.
Clickable versions your team and your users can move through, so a flow can be judged by using it rather than by reading about it.
We put the prototype in front of people, watch where they hesitate, and record what should change before development starts.
Reusable components, spacing and type rules, plus annotated files, so what gets built matches what was approved and the next screen does not start from zero.
Our toolkit
Tools for UX/UI Design and Testing
Early work benefits from being rough and fast. Later work benefits from being precise and shareable. These are the tools we use for each.
Research and Workshops
Used for discovery sessions, journey mapping, affinity sorting and keeping decisions written down where everyone can see them.
- FigJam
- Miro
- Notion
Design and Prototyping
Used for wireframes, interface design, component libraries and interactive prototypes shared by link rather than by file.
- Figma
- Adobe XD
Testing and Validation
Used for unmoderated usability tests, task completion checks and reviewing how existing screens are actually being used.
- Maze
- Google Analytics 4
Accessibility
Used to review colour contrast, focus order, target sizes and whether every action can be reached without a mouse.
- WCAG 2.2 AA
- Contrast checkers
- Keyboard and screen-reader passes
Research and Workshops · Used for discovery sessions, journey mapping, affinity sorting and keeping decisions written down where everyone can see them.
Who this suits
Need Clearer Product UX/UI Direction?
Products Being Redesigned
Existing users, existing habits and real data, where the risk is changing the wrong things.
Startups Before Build
Teams about to commit engineering time who want the flow settled while it is still cheap to change.
SaaS and Dashboards
Interfaces carrying a lot of data, where hierarchy and defaults matter more than styling.
Mobile Apps
Products where screen space is tight and every extra tap is felt.
Teams Without a Designer
Engineering-led teams that need a system and a set of rules they can keep building against.
Conversion Problems
Journeys where people arrive but do not finish, and nobody is certain which step loses them.
What you receive
What the Design Handover Includes
The exact set depends on the agreed scope. A typical UX and UI engagement may include:
- Research summary and findings
- Prioritised UX audit with recommendations
- Sitemap and information architecture
- User flows for key journeys
- Wireframes for important screens
- High-fidelity interface designs
- Mobile, tablet and desktop layouts
- Interactive prototype
- Component library and design system
- Accessibility notes and contrast checks
- Usability test findings
- Annotated developer handover file
- Editable source files in your own workspace
Client project management
How we manage ux/ui design projects
The delivery method stays visible to both teams. Scope, responsibilities, feedback, approvals and handover are documented from the start.
Step 01 Step 02 One shared project workspace
Files, notes, decisions, links and current priorities stay in one shared workspace, giving both teams a consistent source of project information.
Step 03 Weekly status and next actions
Each week we record completed work, current tasks, blockers, decisions required and the next review point, keeping progress visible without constant meetings.
Step 04 Structured feedback and approvals
Feedback is consolidated by the client decision owner, reviewed against the agreed objective, then recorded before the next production stage begins.
Step 05 Documented scope changes
Requests outside the approved scope are documented with their impact on timing, effort and dependencies before either team commits to the change.
Step 06 QA, handover and next steps
Before handover, we review agreed acceptance criteria, test required journeys, document remaining actions and confirm ownership for launch or ongoing support.
Working instructions
What we agree with the client at kickoff
- Nominate one client decision owner for consolidated approvals.
- Share required access, brand assets and source material before the relevant stage begins.
- Return consolidated feedback against the agreed review date whenever possible.
- Use the shared workspace for decisions so important context is not split across channels.
- Raise blockers and changing priorities early so timeline or scope impact can be reviewed before work continues.
Frequently asked questions
UX/UI Design questions we are asked most
UX design decides how a product should work, the structure, the sequence and what each screen is for. UI design decides how that structure looks and feels, including layout, typography, colour and interaction detail. We treat them as one process because a decision in either affects the other.
Not always. If the scope is genuinely settled and the flows are simple, we can move to interface design directly. Where a project has several user types, a long form or a complex journey, a short structural stage usually saves more development time than it costs.
Yes. We can design within your existing brand, extend an existing component library, or take over Figma files created elsewhere. We will tell you if something in the current system is likely to cause problems as you grow.
Yes, at the depth the project supports. That can range from a structured review against usability principles to interviews and moderated or unmoderated testing with real users. We agree the method before starting so expectations are clear.
A focused audit can take one to two weeks. A full design stage for a website is often two to four weeks, and a product or dashboard with many screens takes longer. We confirm a timeline once the number of screens and flows is known.
We design against WCAG 2.2 AA, contrast, focus states, target sizes, reading order and form labelling. Full conformance also depends on how the product is built, so we share our notes with whoever develops it, including your own engineers.
Yes. NovaCraft can take the same project through development, which removes the gap between an approved design and the finished product. We are equally happy handing over to an in-house or third-party team.
Access to your current product or website, an idea of who the users are, any research or analytics you already hold, and someone on your side who can give feedback and make decisions.
Start with the structure
Let’s find out what your product is actually asking people to do
Whether you are planning something new or trying to work out why an existing product underperforms, the first useful step is looking at the journey properly.
Tell us what you are building, who it is for and where you think it is losing people.
Clear scope. Honest assessment. No pressure to buy research you do not need.