Loading...
A structured review of your screens, copy, and flows — mapping where users hesitate, stop, or misread, what's generating support load or drop-offs, and what to address first.
Not a redesign. Not a technical audit.
Friction in screens and flows rarely comes from one thing. It builds up across copy, information order, CTAs, form structure, state messaging, and how much a user has to figure out on their own — until someone hesitates, leaves, or asks the same question again.
This review maps that friction across the agreed scope: your screens, copy, flows, and the decision load placed on your users. What comes back is a structured set of findings — where things are likely breaking down, why, and what to address first.
Not a list of aesthetic observations. Not a technical audit. Not an analytics deep-dive. A structured review that makes the problem clearer, easier to explain, and easier to prioritize — before moving into design, implementation, or further research.
The review covers the agreed scope through these lenses:
Screen structure and information order
whether the layout and sequence support how users actually make decisions
Copy and labels
whether the language is clear, specific, and placed where it's needed
CTAs and action pathways
whether the next step is visible, unambiguous, and well-supported
Forms and input flows
where confusion, hesitation, or abandonment is likely to occur
State messaging
how errors, confirmations, saves, and completions are communicated
User decision load
where users are asked to figure out too much on their own
Consistency
whether screens, copy, and flows are working as a coherent whole
Operational feasibility
whether improvement directions are grounded in what's actually buildable, without requiring code access
Sola Studio is an independent practice run by Yoko Shiina — working across frontend implementation, interface clarity, and accessibility.
Most interface problems don't live in one layer. A confusing flow might be a copy problem, a structure problem, an information order problem, or a decision load problem — often a combination.
Sola Studio's background spans advertising, copywriting, web production, and frontend implementation. That range makes it possible to see the gap between what the interface intends to communicate and what a user actually takes from it — across copy, structure, flow, and operational reality at once.
Because frontend implementation is part of the work, improvement directions are grounded in what's actually buildable and maintainable — without needing to review the code directly.
This isn't a subjective UI opinion. It isn't an automated scan. It's a structured review that connects language, screens, flows, and operational constraints as a whole.
Pricing is based on scope, not a fixed tier. The figures below are starting points — the final cost and timeline are confirmed after the scope is defined.
Light
One focused page or one small flow
A focused review of one agreed page, screen group, or small flow to identify the main friction points across structure, copy, calls to action, form behaviour, state feedback, and decision-making load, with improvement directions and priority notes.
Standard
Key pages or screens + 1–2 core flows
A structured review of agreed key pages, forms, and flows, organising where users are likely to hesitate, stop, misunderstand, make mistakes, or trigger support load, together with improvement directions and priority notes.
Extended
Business / ops screens, multiple states, or deeper review scope
A deeper review for more complex products, internal tools, dashboards, or admin flows, including denser screen logic, multiple states, operational friction, role or permission complexity, and broader supporting context, with clearer scoping for what should be addressed first and what belongs to a follow-on design, implementation, or further research scope.
Japan Market Option
The standard scope can include a Japan Market layer — for teams reviewing Japan-facing pages, forms, flows, or customer journeys.
This review is focused on screens, copy, flows, and the decision load placed on users. The following fall outside that scope.
Design & implementation
No wireframes, visual redesign, or development work
Technical review
No code review, repository access, or detailed technical audit
Analytics & research
No deep analytics analysis, SEO audit, heatmap review, user testing, or quantitative research
Accessibility audit
No formal WCAG compliance evaluation
Legal & compliance
No legal judgment or regulatory review
Guaranteed outcomes
No promises on conversion rates, inquiry volume, or any specific metric
If any of these are what you need, this review isn't the right fit — and that's worth knowing before starting.
UI/UX Review is shaped by the same observation work behind my UX writing and field notes: noticing where people hesitate, where trust is not yet built, and where a small gap in wording, flow, or context can change the experience.
Selected essays have also received independent editorial recognition, including Medium Boost and UX publication features.
A personal essay about turning local observation and a salon owner’s quiet vision into customer-facing messaging — an early lesson in emotional insight, trust, and UX before the term “UX” entered the frame.
Relevant to UI/UX Review because it shows how emotional hesitation, trust, and human interpretation can shape UX decisions.
An essay questioning whether “one interface for everyone” is enough for real inclusion, and exploring how accessibility, Universal Design for Learning, and adaptive UI can point toward more personalized digital experiences.
Relevant to UI/UX Review because it reflects the review lens of not treating users, contexts, or decision needs as one-size-fits-all.
The project starts with an inquiry and discovery call. Scope, materials, access needs, confidentiality setup, quote, contract conditions, payment, and start requirements are confirmed before the review begins.
Send an inquiry and book a call
Share a few short details about your product, target pages, flows, review target, UX or messaging question, implementation context, and what you're hoping to address.
Discovery call
A 30-minute call to understand the context, discuss the service, and check whether the scope is a good fit.
NDA confirmation
For scoped services, an NDA is typically arranged before detailed review and quoting begins. Before an NDA is in place, discussion stays within non-confidential information.
Sola Studio has an NDA template available, and can also review your team's preferred NDA from a confidentiality, scope, and operational-fit perspective where appropriate.
Scope confirmation
After the call, scope details are confirmed through a short form or follow-up messages before the quote is prepared.
Proposal and quote
Once the scope and conditions are confirmed, a proposal and quote are shared for review. The engagement is confirmed after the required contract, payment, and start conditions have been completed.
Invoice and payment
A payment request is issued after the scope and contract documents are confirmed. Unless otherwise stated, listed pricing is shown in USD. Payment is accepted in USD or JPY only. JPY amounts are calculated from the listed USD price using the exchange rate in effect when the invoice is issued. Payments are processed via Stripe. Bank transfer may be available on request for JPY payments only.
Service start
The service starts after the required contract documents, payment, access, materials, and any agreed confidentiality or platform setup are confirmed.
Final sharing session
A 60-minute walkthrough of the findings and shared work output, held as the final sharing step for the scoped engagement.
Review period
After the final sharing step, a standard 5-calendar-day review period is provided to submit clarification questions or comments on minor revisions, unless a different period is agreed in the applicable proposal, contract, or service-specific conditions.
What's the difference between this and the Conversion Friction Series?
The Conversion Friction Series focuses on a single conversion flow — fixed scope, fixed price, no meeting needed. UI/UX Review is for situations where the scope is broader, the problem spans multiple screens or flows, or you want to work through the findings together. If you're not sure which fits, the Estimator is a good starting point.
Do I need an NDA?
Not always. If the review covers only publicly visible pages and flows, it can often proceed without one. If non-public screens, analytics data, or internal materials are involved, an NDA is required before those are shared. This is confirmed in the initial call.
What if I'm not sure what the scope should be?
That's what the initial call is for. You don't need to have the scope defined before getting in touch.
Can you review internal tools or dashboards?
Yes. Operational screens, internal dashboards, and admin interfaces are within scope. These typically require an NDA.
What happens after the review?
If implementation or further specification work is needed, that's handled as a separate engagement. The findings are structured to be usable by your design and development team directly, or as the basis for next steps with Sola Studio.
Do you guarantee results?
No. Findings are expressed as observations and hypotheses grounded in what's visible in the screens and flows. Specific outcomes — conversion rates, inquiry volume, or any other metric — are not guaranteed.
Here are some of the projects we have worked on at Sola Studio.
A real-world internal dashboard project focused on making high-risk CSV-based operational updates safer and easier to handle through the interface. The work covered specification design, validation logic, error UX, and implementation-aware coordination across product, frontend, and backend constraints.
A multilingual site project involving information architecture review, usability research planning, and UX improvement proposals across a site serving up to around five languages. The work focused on booking flows, decision-making content, and structural clarity rather than translation alone.
An end-to-end website redesign covering brand tone, information architecture, UI structure, implementation, and measurement. The work focused on improving product understanding, trust, and user journeys.
If something in your screens, copy, or flows isn't working the way it should
— and you want a clearer picture of what to address — get in touch.
