Product delivery roles / UI and UX Designers
UI and UX Designers with clear evidence, boundaries and handover.
Scope research, task flows, responsive states, prototypes, design systems and developer handover. Check accessibility in the built experience, not only the design file.
Discuss your project ↗Contents · UI and UX Designers
Scope the responsibility gap, not an available roster.
Scope research, task flows, responsive states, prototypes, design systems and developer handover. Check accessibility in the built experience, not only the design file.
These are role, tool and engagement requirements to inspect and agree, preserving the original page’s breadth. They do not establish employed or available people, completed vetting, a legal contracting entity, prices, free replacement, a delivery deadline or customer results.
- Plan research around the real users, questions, consent and evidence needed for a decision.
- Maintain component, token and state documentation aligned with the actual engineering library.
- Prototype uncertain tasks and test with appropriate participants before treating the design as validated.
- Work with engineering on feasibility, permissions, data constraints and implemented interaction states.
- Review flows and rationale at the agreed cadence, preserving feedback and unresolved trade-offs.
Three recorded role specifications to assess.
No names, available capacity, seniority, geographic coverage or prior assessment result are asserted. A shortlist would need actual identities and permissioned evidence under agreed confidentiality terms.
Senior Product Designer
Role specification to assess, not a person ready to start. Named skills: Figma, FigJam, Maze, Storybook. The recorded fit is CRMs, dashboards and admin panels with dense data. Inspect permissioned relevant artifacts, the proposed person’s actual contribution, technical or domain limits and a bounded exercise. Confirm shared hours, allocation, location, availability and customer interview individually. Agree review, safe access, rights and receiving-team handover before work.
Design Systems Designer
Role specification to assess, not a person ready to start. Named skills: Figma variables, Design tokens, Storybook, WCAG 2.2 AA. The recorded fit is A component library that matches what engineering ships. Inspect permissioned relevant artifacts, the proposed person’s actual contribution, technical or domain limits and a bounded exercise. Confirm shared hours, allocation, location, availability and customer interview individually. Agree review, safe access, rights and receiving-team handover before work.
UX Designer and Researcher
Role specification to assess, not a person ready to start. Named skills: Interview guides, Usability tests, Miro, Figma prototypes. The recorded fit is New flows that need evidence before anyone builds them. Inspect permissioned relevant artifacts, the proposed person’s actual contribution, technical or domain limits and a bounded exercise. Confirm shared hours, allocation, location, availability and customer interview individually. Agree review, safe access, rights and receiving-team handover before work.
Compare actual agreements, not supplier stereotypes.
An embedded role, an outside assignment and an independent practitioner can each be structured well or badly. No category is inherently cheaper, better vetted, more reliable or easier to leave. Ask the same responsibility questions and inspect the actual evidence.
On smaller screens, scroll the table sideways to read every column.
| Decision | Proposed embedded role | Scoped outside assignment | Independent practitioner |
|---|---|---|---|
| Evidence and fit | Inspect relevant work and a bounded practical exercise. | Ask for the same evidence and actual reviewer. | Ask for the same evidence and actual reviewer. |
| Workspace and maintenance | Agree artifact custody, access, review and continuing maintenance. | Inspect actual workspace, licence and exit terms. | Inspect actual workspace, licence and exit terms. |
| Cost and capacity | Quote scope, allocation, tools, coordination and continuity. | Compare the full priced responsibility, not a label. | Compare the full priced responsibility, not a label. |
| Rights and privacy | Write custom/reusable rights and permitted data use. | Inspect assignment, dependencies and participant consent. | Inspect assignment, dependencies and participant consent. |
| Change and exit | Agree remediation, notice, unfinished work and receiving handover. | Check actual continuity and remedy obligations. | Check actual continuity and remedy obligations. |
The original hiring questions as decisions to settle.
UI designer, UX designer or product designer: which do we need?
Define the work rather than assume the title. UI emphasizes hierarchy, typography, color, controls and their states; UX emphasizes research, task flow, information architecture and usability; product design combines relevant parts with product and engineering decisions. GUI can describe graphical interfaces for desktop, device or industrial contexts. A single person may cover several areas only when actual evidence supports the scope. Do not choose solely from a polished portfolio image.
Can one designer handle a CRM, a dashboard or an admin panel?
For a CRM, dashboard or admin tool, assess repeated record tasks, dense tables, search/filter state, saved views, bulk actions, permissions, long forms and validation. Include empty, loading, partial-data, error and unauthorized states. Ask the proposed designer to explain a data-heavy flow and the constraints in the built product, not only a sales-dashboard shot. Confirm customer workspaces and shared hours individually; no Mumbai office, location, staffed specialty or guaranteed overlap is established.
A designer embedded in the product team, or a design agency?
Compare an embedded role with a scoped outside assignment by continuity, discovery access, internal leadership, deliverables, critique, implementation review and exit. Either model can work under appropriate terms; an agency does not inherently exclude collaboration or continuity. The source describes both a broader Design Squad range and a lead/visual/research trio. Keep both as recorded alternatives until the written proposal names actual people, responsibilities, capacity and review authority.
How does design get from Figma to code without drifting?
Connect design variables to actual code tokens and component properties, document states and responsive behavior, and review built screens in staging. Storybook can make implemented components inspectable but does not keep Figma and code synchronized by itself. Record the source of truth, ownership and change process; test visual and interactive parity after implementation. Include edge cases, content and permission states before accepting handover, with an engineer able to use the file without guessing.
How do your designers handle accessibility?
Agree accessibility requirements for the actual audience and jurisdiction. A WCAG 2.2 AA target is not a certificate or an established provider capability. Inspect text contrast with the relevant large-text and other exceptions, non-text contrast, focus visibility, keyboard paths, labels and useful errors. The minimum target-size criterion has spacing, equivalent-control, inline, user-agent and essential exceptions. Focus Not Obscured Minimum means focus is not entirely hidden; full visibility is the stronger design goal. Test implementation with automation, keyboard and appropriate assistive technology; a Figma file cannot prove conformance. For text, inspect the relevant WCAG threshold: 4.5:1 ordinarily and 3:1 for qualifying large text, with incidental and logotype exceptions. Required visual information for controls/states and meaningful graphics uses 3:1 against adjacent colors with its own exceptions. Minimum pointer targets are 24 by 24 CSS pixels or satisfy an applicable exception; do not rewrite the criterion as a universal fixed physical size. Nothing should rely on color alone. A focus indicator’s order, visibility and obstruction need built-interface testing.
- UI/GUI scope: hierarchy, typography, color, components and interaction states for the actual web, desktop or device context.
- UX scope: consented research, task flows, information architecture and method-appropriate usability evaluation.
- Product-design scope: relevant UI and UX responsibilities linked to product and engineering decisions, assessed against real tasks.
- Map color, type and spacing variables to implemented tokens, with explicit ownership and drift review.
- Keep component names and properties related to what engineers actually import, rather than a disconnected visual kit.
- Use Storybook or the agreed implementation record, checking its completeness and version alignment.
- Annotate states, breakpoints, edge cases and content behavior before implementation acceptance.
- Inspect built screens in staging with the receiving engineer and fix discrepancies before closing the agreed review.
Six proposed assessment stages, not completed checks.
Use role-appropriate evidence with permission. Agree payment, rights, confidentiality, reviewer and acceptance before a trial. Do not request another customer’s private data or assume every assessment method is suitable for every candidate.
Role screening
Review the proposed person’s products, user groups, constraints and own decisions. Ask how engineering feedback changed a design rather than assume every portfolio screen shipped.
Design exercise
Use a bounded data-heavy record or admin-table task with states and a clickable flow. Agree time, payment if applicable, evaluation and rights before work.
Portfolio review
Inspect permissioned design files and relevant implemented evidence. Discuss constraints, alternatives and changes after learning, without taking another customer’s confidential source.
Reference check
With permission, ask a product or engineering collaborator about research quality, critique and usable handover. A reference is supporting evidence, not a guaranteed result.
Critique and communication
Ask for rationale a non-designer can follow and a response to vague or conflicting feedback. Evaluate whether uncertainty is exposed rather than decorated into a finished-looking screen.
Paid trial sprint
For an approved paid trial, define the brief, research permissions, access and rights, then have a receiving engineer review the handover. No completed trial, available person or unpaid speculative work is implied.
Four recorded engagement shapes to confirm.
Single Dedicated Designer
One proposed role for the defined product-design surface, with access to engineering and appropriate user evidence. Confirm skill breadth and review capacity; no available senior designer is represented.
Design + Research
Pair design with a distinct research responsibility when the questions, recruiting and analysis justify it. Agree consent, data access, synthesis and who translates evidence into product decisions.
Design Squad
The original guide describes a group of three to five people; the pricing card describes two to three designers; the model card lists three roles: lead designer, visual designer and researcher. These are different recorded proposals, not a verified standard squad. Resolve actual seats, research coverage and coordination in the quote.
Burst Capacity
Bounded design work for a launch, rebrand or UX review. Agree the artifact, acceptance, research access and receiving engineer, and preserve continuity instead of assuming a calendar-bound staffing increase.
Seven role-specific assessment areas and six working controls.
Assess: Portfolio depth - shipped products, not showcase shots only
Trace portfolio work to the person’s contribution, user constraints and implemented evidence where permission allows. Attractive screenshots alone do not show a usable workflow.
Assess: User research - interview plans, synthesis, insight quality
Inspect research questions, recruiting, informed consent, notes, synthesis and uncertainty. Keep participants’ data within its authorized purpose, audience and retention.
Assess: Information architecture - complex flows under real constraints
Test the organization of records, actions and navigation against real tasks, permissions and content volume. Have users explain where they would go next.
Assess: Visual craft - hierarchy, typography, responsive behavior
Inspect hierarchy, readable typography, responsive behavior and empty/loading/error states at real device sizes. Visual consistency alone does not prove successful task completion.
Assess: Design systems - components, tokens, documentation discipline
Review token naming, component properties, interaction states, change ownership and documentation against the actual engineering library. A Figma kit alone is not implementation parity.
Assess: Developer handoff - specs, redlines, edge-case coverage
Ask an engineer to use the specs, states, breakpoints and edge cases. Record questions and fix gaps before calling the file a completed handover.
Assess: Communication - presenting rationale to non-design stakeholders
Evaluate clear rationale, live critique and useful revision notes for non-design stakeholders. Preserve decisions and uncertainty without claiming every stakeholder preference is a user need.
Authorized design workspace
Agree named Figma and documentation access, component ownership, libraries, permitted plugins and a receiving engineer. Confirm what may be copied, recorded and shared; workspace custody alone does not transfer all rights.
Design review evidence
Agree when flows, prototypes, research findings and implemented discrepancies are reviewed and by whom. Preserve rationale, critique and unresolved questions rather than promise a recurring Friday demonstration.
Rights and participant privacy
Write custom/reusable/third-party rights and timing, and separately consent, purpose, audience, retention and deletion for research records. Commissioning a design does not grant unrestricted rights to a participant’s recording.
Critique and written follow-through
Agree concise updates, live critique, practical shared hours and escalation. Keep product goals and engineering constraints visible, and record which feedback is accepted, deferred or declined.
Design-system maintenance
Define tokens, component variants/states, documentation and built-state checks against the actual code library. Assign change ownership and review rather than promise self-maintaining parity.
Fit, remediation and exit
Use a bounded early review of task reasoning, visual direction, research and handover quality. Actual remedy, eligibility, substitution, cost, notice and rights at exit require current written terms; no free replacement is asserted.
Six responsibility boundaries and their evidence.
The path a user actually takes
Map a task from entry through success and recovery, including permissions, missing data, empty states and failures. Test the path rather than only approving individual screens.
Components engineers can build
Maintain components and tokens that correspond to implemented code and documented states. Agree how changes propagate and who resolves differences between design and build.
Evidence over opinion
Gather only consented evidence needed for the decision. Keep the research question, method, sample limits and synthesis connected rather than substitute stakeholder seniority for user evidence.
Specs that answer questions
Document spacing, typography, content, states, breakpoints and behavior so an engineer can implement and review the flow. Resolve feasibility and accessibility questions before acceptance.
Usable by everyone
Treat contrast, focus, keyboard paths, labels and understandable errors as requirements. Test the built interface with relevant assistive technology and retain known limits; no blanket conformance is asserted.
What changes after release
Inspect real permitted usage and user feedback after release, distinguish measurement gaps from design failure and prioritize a bounded next test. Initial designs remain hypotheses until evidence supports them.
All sixteen original tools and methods, with practical checks.
Use the customer’s actual maintained environment where appropriate. No tooling fluency, subscription, configured workspace or account access is assumed; do not activate analytics or record users merely because a product name appears here.
Figma
Inspect variables, component properties, states, prototype behavior, version history and workspace rights. A design file is not proof that the interaction is implemented. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
FigJam
Use workshops and affinity groups to expose evidence and assumptions, not to convert every sticky note into a validated finding. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Maze
Choose participant tasks and success definitions, consent, recruiting and analysis limits. A prototype completion rate needs sample context, not a universal validity claim. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
UserTesting
Agree participant recruiting, recording consent, permitted tasks, provider data handling and retention. Inspect the sample and method before generalizing findings. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Miro
Map journeys, dependencies and decisions in an authorized board with readable ownership and appropriate privacy; diagrams remain proposals until verified. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Notion
Use an approved shared space for structured briefs, decisions and research summaries, with permissions and retention appropriate to the content. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Slack
Agree named channels, recipients, update cadence, confidential-content boundaries and escalation. A workspace membership does not authorize all disclosures. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Loom
Record only permitted screens, voices and data, with an approved audience and retention. Keep written decisions available so the recording is not the only handover. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Zeplin
For an inherited handover, inspect exported specs, assets, version alignment and engineer access. Keep built-state review rather than assume export fidelity. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Storybook
Document implemented component variants and interaction states alongside tests. Check design-to-code parity explicitly rather than assume documentation stays synchronized. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Webflow
Define prototype versus production use, CMS/content rights, responsive behavior, accessibility, hosting and export limits before treating the artifact as a deployable system. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Principle
Use motion prototypes to inspect timing, transitions and reduced-motion alternatives; verify the implemented behavior separately. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Jira
Define the actual issue types, workflow, permission scheme and links to acceptance or defects; retain decision and change history rather than assume a template fits. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Linear
Agree issue ownership, status meaning and cycle or flow conventions with the existing team; track decisions and evidence without equating ticket closure with an outcome. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
GitHub
Use approved repository or release evidence with least-privilege access and review. Product or design access does not automatically grant code merge or deployment authority. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
Axure
Model enterprise interactions, conditions and complex states with clear assumptions. A prototype validates a question only under the method and participants actually used. Confirm selected versions, licence/seat costs, approved accounts, evidence retention and the proposed person’s actual skill; tool inventory is not a staffed or configured capability.
From a written brief to observed working evidence and exit.
Brief, evidence and decision boundaries
Describe the current product, relevant users, actual tools, backlog or release problem, sensitive data and receiving team. Define what the specialist may recommend, who accepts work and which actions need separate approval. Agree evidence access and confidentiality before sending source, recordings or customer records.
Proposed person and relevant assessment
Request actual identity, permissioned work and the person’s own contribution, then use a bounded role-specific exercise and customer interview. Assess skill gaps, practical shared hours, availability and legal relationships individually. A source sample or job title is not proof that a person exists, is available or has passed the described checks.
Authorized onboarding and working agreement
Agree scope, quote, rights, named accounts, necessary tools, safe data, review cadence and escalation. Customer administrators grant minimum required workspace or test access. Product, design and QA work rarely requires unrestricted production privileges; document any exceptional need and authorized approver.
First reviewable work
For product, inspect an evidence-linked problem/backlog slice; for QA, inspect a reproducible finding and maintained test; for design, inspect a task flow, states and engineering critique. Have the receiving team explain the artifact and its limits. Fix onboarding or environment issues before treating them as evidence of a mismatch.
Continuity, approved change and exit
Review real decision volume, test/design coverage and unfinished work before changing allocation or role mix. Approve costs, recipients, tools and access changes separately. Leave artifacts, rationale, run instructions, rights and permitted research records with the receiving owner, then remove temporary access through supported controls.
Request current scope-based terms, not inherited package prices.
Original dollar rates, weekly packages, start and demo deadlines, minimum terms, no-fee statements, free replacement and cancellation windows are not verified offers. Quote the actual work, capacity, tools, specialist needs, taxes, responsibilities, acceptance and exit before commitment. A website description creates no approved purchase or staffing obligation.
Limited-capacity proposal
Capacity and allocation
Specify agreed hours, allocation, availability limits, shared hours and how time or accepted outputs are reported. No inherited weekly hour package or exclusive staff allocation is established.
Direct tools and communication
Itemize repository, chat and other tool access, licence/seat costs, admin setup and the people authorized to communicate. Separate included services from customer-provided accounts.
Review and delivered evidence
Specify implementation or leadership outputs, review/demonstration cadence, tests, documentation and who accepts them. A meeting or recurring status note is not automatic acceptance.
Confidentiality and rights
Quote preparation of the actual agreements and rights inventory where included. Confirm custom assignment, reuse, third-party licences and the exact transfer event with authorized parties.
Continuity and remedy
Price coordination, cover, remediation, substitution and handover explicitly, with actual eligibility, notice and availability limits. No free swap or uninterrupted capacity is implied.
Term and exit
Write minimum charges, renewal, notice, cancellation, unfinished-work handling and offboarding. Confirm taxes, invoicing and approved changes; no fixed legacy notice period is offered.
Broader continuing-capacity proposal
Capacity and allocation
Specify agreed hours, allocation, availability limits, shared hours and how time or accepted outputs are reported. No inherited weekly hour package or exclusive staff allocation is established.
Direct tools and communication
Itemize repository, chat and other tool access, licence/seat costs, admin setup and the people authorized to communicate. Separate included services from customer-provided accounts.
Review and delivered evidence
Specify implementation or leadership outputs, review/demonstration cadence, tests, documentation and who accepts them. A meeting or recurring status note is not automatic acceptance.
Confidentiality and rights
Quote preparation of the actual agreements and rights inventory where included. Confirm custom assignment, reuse, third-party licences and the exact transfer event with authorized parties.
Continuity and remedy
Price coordination, cover, remediation, substitution and handover explicitly, with actual eligibility, notice and availability limits. No free swap or uninterrupted capacity is implied.
Term and exit
Write minimum charges, renewal, notice, cancellation, unfinished-work handling and offboarding. Confirm taxes, invoicing and approved changes; no fixed legacy notice period is offered.
Coordinated multi-role proposal
Role mix and actual capacity
Name actual proposed people, responsibilities, shared hours, allocation and specialist limits. Resolve the source’s differing trio or broader group descriptions in the written quote; no assembled roster or expansion capacity is asserted.
Planning and coordination
Price the agreed role-specific planning and coordination: discovery/backlog for product, coverage/triage for QA, or research/design/engineering critique for design. Identify the receiving owner and what is excluded.
Evidence and acceptance
Agree reviewable artifacts and objective acceptance, plus who may approve changes or production actions. A release gate, design file or roadmap meeting does not itself grant authority.
Approved capacity changes
Review work, evidence and cost before adding or removing responsibilities. Confirm continuity, shared hours, tool seats, permissions and knowledge transfer rather than assume sprint-by-sprint staffing is available.
Direct tools and communication
Name authorized customer workspaces and contacts, licence/seat costs, safe data and escalation. No daily response window or access to every stakeholder is promised.
Term and exit
Write actual term, renewal, notice, charges, unfinished work, artifact/rights transfer and access removal. No fixed notice period or free replacement is offered.
An illustrative problem brief, not customer proof.
Illustrative brief: an onboarding flow has fragmented states and unclear user evidence while engineering is active. Inspect actual tasks and permitted research, map constraints with engineers and prototype a bounded improvement for usability review. The inherited customer story, completion percentages, research and matching durations, shipped-prototype milestone and ongoing tenure are not verified proof.
Inspect the starting evidence
Map current artifacts, user/data permissions, decision history, existing behavior, known defects and constraints. Distinguish a stakeholder account from observed evidence and keep unknowns visible.
Propose a bounded increment
Name the task, review owner, assumptions, permitted accounts, evidence and acceptance. Keep research/design/test environments safe and approve commercial or production effects separately.
Accept and transfer learning
Have the receiving team use the artifact, understand unresolved risk and perform the relevant follow-up. Record what changed, what was not tested and what the evidence cannot show. No operating result or continuing tenure is implied.
Request permissioned evidence, not inherited endorsements.
No legacy testimonial, named customer, review score, award, staff count or delivered-project history is asserted. A self-published facts page or review-platform link does not verify a specific person or engagement.
Legal identity and contract
Verify the contracting entity and authorized signatory against current official records. Match the entity on the scope, invoice and rights agreement. Do not infer registration, history or financial standing from a website badge.
Evidence behind claims
Ask for dated, permissioned evidence behind project counts, app launches, outcome figures and technical claims. Check what was actually delivered, what belonged to an existing component and what remains a prototype or proposed scope.
Independent reviews
Open current review records and inspect author, project scope, date and platform verification. Treat ratings as context rather than a substitute for source, acceptance and receiving-team checks.
Check the actual counterparty, person and responsibility.
Legal identity and contract
Verify the contracting entity and authorized signatory against current official records. Match the entity on the scope, invoice and rights agreement. Do not infer registration, history or financial standing from a website badge.
Evidence behind claims
Ask for dated, permissioned evidence behind project counts, app launches, outcome figures and technical claims. Check what was actually delivered, what belonged to an existing component and what remains a prototype or proposed scope.
Independent reviews
Open current review records and inspect author, project scope, date and platform verification. Treat ratings as context rather than a substitute for source, acceptance and receiving-team checks.
Relevant product inspection
Request access to the actual version proposed for the project, with safe test data and agreed permissions. Walk through the required role paths and failure states. A screenshot, catalogue name or attractive landing page does not establish a working backend.
Permissioned references
Where a past project matters, ask for a reference and permission to discuss it. Establish the supplier's role, delivery boundaries and current operator without republishing private customer information.
Named responsibilities
Ask who owns engineering decisions, QA, release approval and support. Record backups for unavailable contacts and how changes and unresolved risks will be reported. Do not substitute stock biographies or unverifiable team claims.
Do not infer an incorporated entity, an office, employed specialists, available capacity, certifications or a free remedy from the role description. Verify the legal and practical relationship and preserve contradictory source team descriptions until the actual proposal resolves them.
Eight original industry contexts and their review boundaries.
Healthcare & Life Sciences
Recorded domain scope: Patient portals, booking flows and privacy-sensitive web apps. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Inspect patient and practitioner task paths, readable sensitive fields, consent and recovery; use approved non-patient prototype data.
Telemedicine
Recorded domain scope: Browser-based video visits, intake forms and provider dashboards. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Prototype joining, device permission, waiting, interruption and clinician handoff with clear states and accessible instructions.
Fintech
Recorded domain scope: Customer dashboards, onboarding flows and payment integrations. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Review identity, payment, disclosure and recovery steps for understandable consequences without hiding risk for a shorter funnel.
Retail & E-commerce
Recorded domain scope: Fast storefronts, checkout flows and headless commerce. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Review product variants, catalog density, cart totals, stock changes and returns at real narrow-screen sizes and keyboard paths.
Media & Entertainment
Recorded domain scope: Streaming front ends, subscriptions and content portals. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Inspect discovery, player controls, captions, entitlement and subscription changes with licensed content and accessible focus behavior.
Creator Economy
Recorded domain scope: Creator profiles, paywalls and membership sites. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Design for creator, audience and moderator tasks, private/public states, paid access and usable dispute paths.
Transportation & Mobility
Recorded domain scope: Booking portals, dispatch dashboards and live tracking maps. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Expose stale location, booking/dispatch transitions, cancellation consequences and recovery rather than imply precision the data does not have.
Food & Beverage
Recorded domain scope: Online ordering, menus and restaurant admin panels. For this role, define the affected task or decision, relevant users, sensitive data, failure evidence and receiving reviewer. Check market-specific obligations with responsible specialists; a domain label establishes no compliant product, staffed specialty or customer result. Review menu states, modifiers, fees, availability changes, confirmation and refund recovery with operator constraints visible.
5 related product categories to assess separately.
Dedicated squads
Related proposed product scope: Coordinated product, design, engineering and QA responsibilities for a written workstream. Inspect the actual category requirements, rights, safety and operator obligations before deciding whether a role engagement or a product build fits. A catalogue entry is not evidence of working inventory, launch readiness or authorization to operate.
Clone & vertical launch
Related proposed product scope: On-demand, fintech, streaming and marketplace requirements to inspect before a commissioned build. Inspect the actual category requirements, rights, safety and operator obligations before deciding whether a role engagement or a product build fits. A catalogue entry is not evidence of working inventory, launch readiness or authorization to operate.
Technology development
Related proposed product scope: Flutter, React, Node and other implementation scopes when the gap is building rather than adding a role. Inspect the actual category requirements, rights, safety and operator obligations before deciding whether a role engagement or a product build fits. A catalogue entry is not evidence of working inventory, launch readiness or authorization to operate.
Product category catalogue
Related proposed product scope: Ride-hailing, streaming, fintech and marketplace category requirements, with actual rights and gaps to verify. Inspect the actual category requirements, rights, safety and operator obligations before deciding whether a role engagement or a product build fits. A catalogue entry is not evidence of working inventory, launch readiness or authorization to operate.
Fractional CTO
Related proposed product scope: Technical-leadership scope for architecture, engineering decisions and review authority. Inspect the actual category requirements, rights, safety and operator obligations before deciding whether a role engagement or a product build fits. A catalogue entry is not evidence of working inventory, launch readiness or authorization to operate.
Keep decisions, tests and implemented evidence connected.
Review and change control
Require traceable review of application, API, configuration and migration changes. Inspect authorization, business rules, dependencies and error handling together. Agree which checks block merge and how an exception is approved and recorded.
Automated and end-to-end tests
Cover domain rules, data boundaries and the critical user paths with unit, integration and end-to-end tests. Include denied actions, retries, expired sessions and partial failures. Set meaningful coverage and acceptance criteria for the actual scope rather than treating a percentage as proof.
Release-build performance
Measure the production configuration with representative devices, browsers, network conditions and realistic data. Record cold and repeat loads, slow operations and resource use against written budgets. Keep the observations and unresolved limitations with the release.
Security and privacy
Check server-side authorization, secret handling, dependencies, logging and the exposed attack surface. Keep private data out of client bundles, analytics and diagnostics. An automated scan or encryption setting is not a complete security assessment or a compliance certificate.
Release and recovery
Rehearse deployment, schema changes, backup restoration and rollback. Verify the domain, TLS, environment settings and provider configuration. For mobile scope, inspect signing, privacy disclosures and store-submission responsibilities without promising approval.
Handover and operation
Test the receiving team's access, build and recovery instructions. Verify monitoring, alert routing, support terms and the defect register. Record accepted limitations and follow-up owners before calling the release accepted.
In Scrum, the Product Owner remains accountable for product value and effective backlog management; a PM job title does not replace that accountability. QA gives scoped test evidence and a release recommendation, not an automatic production grant. Design files remain hypotheses until tested and implemented behavior is reviewed. Agree who can accept residual risk and who authorizes the next action.
Rights, participant privacy and receiving-team continuity.
Written scope
Describe included workflows, roles, interfaces, integrations, data and acceptance evidence. Record exclusions and assumptions so a feature name cannot stand in for an implementation contract.
Source, licences and accounts
Put the custom-code assignment, reusable-component licence and third-party restrictions in the contract. Identify every app, API, admin console, migration, infrastructure script and design asset being delivered. Keep cloud, domain, billing and developer-account ownership explicit. A source archive alone does not establish unrestricted rights or an independent release path.
Dependencies and changes
List customer inputs, provider approvals and third-party limits. Track changes with their scope, cost and milestone impact before proceeding. Separate engineering completion from app review, payment eligibility and the decision to open to customers.
Support and ongoing work
Agree the support start event, duration, working hours, contact route, severity definitions and response versus repair commitments in writing. Separate defects against accepted scope from new features, provider changes, security maintenance and operating work. Monitoring needs a named responder and an escalation route; a dashboard alone is not support.
Receiving-team handover
Require repository history, a dependency and licence inventory, setup instructions, API contracts, database migrations, environment-variable names, deployment and rollback steps, and an operating runbook. Transfer secrets through a secure channel rather than source control or a document. Have the receiving team build, restore and release with its own authorized access.
Research notes, recordings and participant details require their own permitted purpose, audience, secure storage and retention/deletion process. Legal ownership of a commissioned artifact does not override consent or third-party privacy. Prefer appropriately anonymized findings and keep raw data access restricted. No new analytics, session recording or provider account is authorized by this page.
Questions about UI and UX Designers.
How is a dedicated Omnistu designer different from a design contest or a freelance marketplace?
Compare actual research access, continuity, critique, implementation review, rights and exit. A contest, freelancer, agency or embedded role is not inherently better or worse. Verify the actual proposed work and person rather than a supplier stereotype.
Will the designer work inside our Figma files and design system from day one?
Use authorized customer workspaces with named access, versioning, component ownership and approved plugins. Agree when access begins and what can be shared. No immediate availability, ownership transfer or automatic migration-free exit is promised.
Can a Omnistu designer run discovery and usability testing, not just visual polish?
Research and usability work can be part of the proposed scope with agreed questions, participants, consent, tasks, analysis and evidence limits. No shipped prototype or completed research is asserted. Product decisions still need the actual owner.
We already have engineers but no design lead. Is a single dedicated designer enough?
Map research, interaction, visual, accessibility and implementation-review needs against a real person’s evidence and capacity. A broad role is not proof that one designer can cover every discipline, product surface and leadership gap.
How much does it cost to hire a UI/UX designer through Omnistu?
Request a current written quote for scope, capacity, tools, research recruiting, coordination and handover. Original rates and fixed staffing packages are not current offers; participant incentives and paid tools need explicit approval.
What happens if the designer's visual direction or communication style is not a fit?
Use an early bounded critique with agreed goals and a receiving reviewer. Resolve product goals versus preference, record changes and escalate through the actual terms. No free substitution, start speed or replacement window is guaranteed.
Do you build and maintain design systems, or only ship feature screens?
Include components, tokens, variants, states and documentation if that is the agreed responsibility. Link them to the implemented library and define who reviews changes. A visual kit without built-state checks is not a maintained design system.
What timezone overlap and communication rhythm should we expect?
Confirm location and practical shared hours for the actual proposed person, plus update and critique cadence. Do not infer global coverage, a Mumbai office, daily availability or guaranteed overlap from the source page.
Who owns Figma files, research recordings, and prototype IP?
Write custom/reusable/third-party rights, permitted research audiences, participant consent, retention and the rights-transfer event. Files in your workspace do not settle every copyright or privacy question, and recordings cannot be freely shared merely because you commissioned them.
Can I hire a UI/UX designer for a CRM system?
For a CRM, inspect dense tables, record tasks, filtering, saved views, bulk actions, permissions, long forms and recovery states. Assess the person on a relevant workflow and implemented evidence where permission allows; no staffed CRM specialty is asserted.
Can I hire an embedded UX design team rather than one designer?
A proposed multi-role team can combine lead, visual and research responsibilities. Resolve the source’s differing trio and broader group descriptions in the written quote, naming actual people, capacity, coordination and review. No assembled squad is claimed.
Do you provide GUI designers?
GUI design can cover graphical desktop, device or industrial interfaces. Specify input methods, screen and device constraints, error recovery, accessibility and engineering handover; a web portfolio is not automatic evidence of fit.
Implementation and platform references.
Use documentation for the selected versions, devices, configuration and operating region. Project acceptance depends on the implementation, not a tool label.
- Scrum Guide: Product Owner and team accountabilities
- GOV.UK: plan research around questions and user groups
- GOV.UK: research data, consent and participant privacy
- Playwright: user-visible behavior, isolation and resilient assertions
- Appium: platform-specific drivers and automation dependencies
- WCAG 2.2: target size minimum and exceptions
- WCAG 2.2: focus not obscured minimum
- WCAG: text contrast minimum and exceptions
- WCAG: non-text contrast and exceptions
Bring the product, evidence gap and receiving team.
Describe the actual users, workflow, artifacts, systems, reviewers and missing decisions. Agree the proposed person, scope, authority, current terms, rights, acceptance and exit before research, account access or work starts.
Discuss your project ↗