Yoko ShiinaExperience

Experience across business, design and engineering

My experience spans advertising strategy and creative direction, website design and development, and software engineering. Each role involved different responsibilities, from understanding customers and business goals to building and improving software.

The entries below describe the work I took on, the challenges I addressed and the results where available. Together, they show the range of experience behind my work today as a product designer specialising in UX architecture. My software engineering experience informs that work and allows me to contribute to implementation when needed. For a closer look at my UX architecture work, see the case study.

See how a project worksRead the case study

Software Engineer

Play'n GO

Context
Online game company. A distributed Scrum team working on game titles and internal developer tools
Worked with
Product owner, team lead, QA, engineers, the framework team
Period
May 2024 – Jun 2025
Stages
  • Listen
  • Align and decide
  • Hand over

At Play'n GO, my main work was refactoring legacy game code for updates to an in-house UI framework, fixing bugs, and developing features for an internal deployment tool. I also helped improve how the team worked: defining what engineers should check before handing work to QA, documenting game-specific integration knowledge, and making actions and errors clearer in the parts of the internal tool I worked on.

The pre-QA checklist

Situation

Engineers did not share a clear understanding of what they should check before handing changes to QA. Some fixes reached QA with problems that a basic run could have caught. Others had already been checked, but engineers and QA disagreed about where their responsibilities began and ended. A "Dev testing" status was added to tickets, but its scope was never defined, and the same disagreements kept returning.

What I did

I proposed that the team define the checks together. I asked the team lead for an initial draft and used it in a working session to discuss what belonged to development and what should remain with QA. I documented decisions as we made them, and we finalised the checklist in a second session.

The checks covered launching a game, loading animations, settings, basic gameplay and sound, as well as common framework-specific failure patterns. Longer test runs remained with QA. My aim was not simply to create a document, but to establish a shared understanding of what was expected.

Result

The checklist became part of the normal development process. Engineers could show what they had checked, QA knew what to expect, and the team lead could explain the agreed scope to the product owner. The recurring friction stopped.

Framework integration and documentation

Situation

Our team integrated updates to an in-house UI framework across a portfolio of around 300 game titles. The titles differed in structure, behaviour and age, so major updates could cause games to freeze or behave unexpectedly. Solutions often depended on the individual game, and much of that knowledge remained with experienced engineers or in chat conversations rather than being consistently documented.

What I did

I refactored legacy game code using TypeScript, Java and object-oriented design, fixing bugs and improving maintainability as I integrated framework updates. I also documented integration steps, known issues, workarounds and code examples, and shared them in a place accessible to my team and other teams.

Internal developer tool

Situation

An internal tool for bulk deployment was useful but difficult to navigate. Its many coloured buttons gave little indication of which actions belonged together or what would happen when they were pressed. Engineers often explained the steps to each other verbally. Tickets could start as broad ideas without detailed designs or specifications, and messages in the built-in terminal were not always clearly identifiable as errors.

What I did

I developed UI features using Vue 3, Electron, TypeScript and Vite, including the flow for selecting and configuring deployment targets. I broke broad tickets into smaller tasks and worked on bug fixes and maintenance. Within the parts I was responsible for, I made terminal errors easier to recognise and added short explanations of what buttons would do.

I also facilitated a team retrospective, drawing on my CSM and CSPO knowledge.

Built with
TypeScript, Vue 3, Electron, Vite, Java, GitHub, TeamCity, Octopus

Frontend Engineer — Learning Platform MVP

Online learning platform

Context
Freelance. Building the MVP for a new learning platform that issues course completion certificates
Worked with
CEO, CTO and designer in a four-person distributed team
Period
Apr 2023 – Apr 2024
Stages
  • Align and decide
  • Hand over

At a four-person startup team for an online learning platform, I led the front-end architecture and implementation of a learning platform MVP. I built the user-facing and admin interfaces, including login and certificate issuing. With no separate UX design phase, I also had to work out how the experience should behave when a process failed or was interrupted, making those decisions alongside the code and data flow.

Failure handling and recovery

Situation

The Figma designs covered screens and selected button states, but not what should happen when a process failed or someone returned after closing the browser before it completed. These behaviours needed to be defined during implementation.

What I did

I designed and implemented a connected flow from login to certificate issuing. I added handling for failures and retries, making each step's status and required action clear.

For interrupted processes, I stored a non-sensitive status in localStorage so the application could check the result on a return visit and resume certificate issuing when needed. I ran repeated smoke tests to check both the user experience and the underlying data flow.

Result

The resulting flow handled failures and return visits, rather than relying only on the successful path shown in the original designs.

Data handling and API integration

Situation

The application needed to handle authentication, persistent user data and information reused across screens. Decisions about where data should live, how it should be fetched and what the APIs should return affected both the user experience and implementation.

What I did

I chose between database storage, NextAuth sessions, React Context and localStorage based on data sensitivity, persistence and reuse. I also used server-side rendering, client-side rendering and static generation according to each page's needs.

I worked with the CTO to select Prisma and refine data requirements, API specifications and schema decisions as the MVP evolved. I implemented parts of the Next.js API routes, using Prisma for database access and shaping responses for front-end use. I also raised performance considerations, including where filtering and sorting should happen.

Front-end delivery and collaboration

Situation

Libraries were changing quickly, and reliable examples for integrating them with Next.js, especially for failure and recovery cases, were limited. The team also needed to keep technical decisions aligned while working asynchronously across time zones.

What I did

I built the front end with Next.js, React and TypeScript, turning Figma designs into accessible, reusable components with fully custom styling. I developed both user-facing and admin screens, implemented authentication with NextAuth, and wrote focused unit tests with Jest and React Testing Library. I worked through library integration issues and updated the implementation as dependencies changed.

I documented user flows and technical decisions so the CEO, CTO and designer could follow changes asynchronously. I also raised technical trade-offs early, presenting alternatives and fallbacks to help the team make decisions as requirements evolved.

Built with
Next.js, React, TypeScript, Node.js, Prisma, NextAuth, GCP, Figma, Jest, React Testing Library

Frontend Developer

LSEG TORA

Context
Financial B2B SaaS. Worked across product development in Romania and internal tool development in Tokyo
Worked with
Front-end engineers, a designer, QA, team lead and product owners in Romania; a manager and engineers in Tokyo
Period
Apr 2022 – Mar 2023
Stages
  • Listen
  • Align and decide
  • Follow through

At LSEG TORA, I worked across two teams. With the Romania-based team, I developed and maintained components for financial SaaS products within a detailed design, review and testing process. In Tokyo, I led the front-end development of an internal PDF reporting MVP, helping turn a time-consuming manual process into a simple workflow. The two projects gave me experience in both maintaining established products and translating business requirements into working software.

Core products and shared UI

Situation

The team worked from detailed Figma designs and carefully scoped tickets, with code changes requiring approval from multiple reviewers. Even button states and focus styles were specified precisely. However, some interaction behaviour was less clearly defined, such as what should happen after an action or when a modal was closed. Answers were sometimes spread across tickets, discussions and previous implementations, and it was not always clear who had made a decision.

What I did

I built and maintained UI components for financial SaaS products using React, TypeScript, Redux, SCSS and Tailwind CSS. I also improved and refactored the shared UI library used across applications, updating Storybook alongside component changes. I wrote tests with Jest, React Testing Library and Cypress, and took part in code reviews and specification checks.

When interaction behaviour was unclear, I checked with the designer, senior engineers and product owners. Sometimes there was an existing decision to follow; other times, the team needed to work out what should happen. Working with colleagues in Romania from Tokyo also meant coordinating questions and decisions asynchronously across time zones.

Internal PDF report generator

Situation

Each month, an engineer manually prepared PDF reports for major clients in Japan, using SQL to retrieve financial data, Excel to create charts and PowerPoint to assemble the reports. The process could occupy the engineer and their computer for up to around ten working days a month. Report types and the rules for producing them were embedded in the existing work rather than clearly defined in one place.

What I did

When the manager raised the idea of automating the process, the team agreed to build an MVP, and I took responsibility for the front end. I interviewed the engineer doing the work and examined existing reports to identify and classify the different report types. I turned this into a straightforward workflow: select a client, a reporting period and an available report type, then generate the PDF directly.

I built the interface with React, TypeScript and Material UI. I worked with another engineer on Prisma-based data access, writing the code that called the existing queries. I used Chart.js for chart generation and selected Puppeteer for PDF output, working through the layout details needed for multi-page reports, including logos, headers, footers and page numbers.

Result

We tested the MVP with selected real reports, generating PDFs in approximately 5–20 seconds per report. Based on those trials, we estimated that the monthly reporting workload could be reduced from up to around ten working days to a few hours. The engineer who had been preparing the reports was very pleased with the result, and the manager responded positively to the clear workflow and the reduced workload. By the time I left, the manager had material to present the tool internally.

Built with
React, TypeScript, Redux, SCSS, Tailwind CSS, Material UI, Storybook, Jest, React Testing Library, Cypress, Chart.js, Prisma, Puppeteer, PostgreSQL

Web Developer & UX Consultant

Freelance

Context
More than 20 websites across e-commerce, hospitality, the public sector and transport
Worked with
Business owners and in-house teams, translation and localisation teams, designers, implementation partners
Period
May 2013 – Sep 2020
Stages
  • Listen
  • Align and decide
  • Hand over
  • Follow through

I worked on more than 20 websites, from small local businesses to multilingual projects for global brands. My responsibilities varied by project. Sometimes I handled the process from client interviews and information architecture through design and development. On other projects, I focused on site structures, wireframes, user flows and client coordination. I also built responsive websites within limited budgets and existing codebases. Throughout this work, I kept both the business goals and the needs of the people using the sites in view.

A beauty appliance manufacturer

Situation

The company's website had grown without a clear structure. Product information was limited, mobile support was poor, and the pages focused on describing features rather than helping people decide what to buy. Looking at the site as a potential customer, I found that it did not answer many of the questions I would have before purchasing. Staff were also spending time answering the same product and support enquiries repeatedly. The online store faced similar challenges in helping customers understand and compare products.

What I did

I worked directly with the CEO to clarify the brand's values, direction and tone, then translated them into the website's structure, content and visual design. I rebuilt the corporate website with clearer navigation, responsive layouts and product pages organised around the questions people needed answered before buying. I also created the brand concept and story pages.

To make practical information easier to find, I built a categorised FAQ from recurring questions collected by staff handling customer enquiries and their existing email responses. I also added information about repairs, warranties, manuals and policies. After launch, I used Google Analytics and Search Console to review how people used the site and identify further improvements.

For the Rakuten online store, I redesigned and implemented the store template, navigation and product pages within the marketplace's constraints. I organised each page around buyers' concerns, explaining how the product's features related to what customers wanted to achieve. I adjusted the copy and visual direction to reflect the positioning of each product.

I also planned and delivered the company's first social media campaign of this kind, connecting the participation process, landing page, advertising, ambassador outreach and entry management. When entries were below target after launch, I introduced an additional promotion channel to help reach the campaign goal.

Result

Following the corporate website relaunch, sessions increased by 174%, the bounce rate fell from 82.2% to 76.8%, and average session duration increased by 30 seconds. Staff also reported fewer repeated enquiries about topics covered in the FAQ.

On the online store, monthly unit sales averaged around 39 times higher for one product and 2.4 times higher for two others, comparing the month before the changes with the following four-month average.

The social campaign reached 107% of its entry target, and ambassador registrations increased by 111%.

Multilingual websites

Situation

I contributed to two multilingual website projects, one for a global home appliance manufacturer and one for a resort hotel, each covering around five languages. Both required clear information structures and user journeys to help visitors understand their options before purchasing or booking.

What I did

As part of the project direction team, I organised requirements and prepared sitemaps, main user flows and wireframes. For the resort hotel, I reviewed how visitors checked availability, compared room types and moved towards booking. For the appliance manufacturer, I considered what people needed to understand and compare expensive products, including specifications, dimensions and real-world use. I proposed presenting information in stages and using images that showed the products in context.

I also helped prepare task scenarios and follow-up questions for qualitative usability research, including organising questions about the overall site and individual pages. I contributed design briefs and specifications, coordinated with designers on some projects, reviewed completed designs and worked with production colleagues through implementation and launch.

Built with
HTML, SCSS, JavaScript, WordPress, jQuery, Bootstrap, Rakuten CMS, Photoshop, Illustrator, Sketch, Google Analytics, Google Search Console, Facebook Ads

Account Strategist — Acquisition & Creative Direction

Recruit

Context
Advertising for hair salons, in beauty and lifestyle
Worked with
Salon owners and staff, photographers, models, the sales and client teams
Period
Jul 2010 – Oct 2012
Stages
  • Listen
  • Align and decide
  • Follow through

I managed advertising for more than 35 salon clients while also developing new business. My work covered customer acquisition strategy, positioning, copywriting, promotional offers and pricing, and creative direction for photography. I was responsible for both client advertising performance and commercial targets, including renewals and revenue. Understanding each salon's business and customers was central to making the advertising effective.

Understanding the business and its customers

What I did

I began by listening to salon owners and staff, understanding their goals, and looking at how the business was performing. I reviewed customer visits, repeat visits, average spend and popular services, then compared those figures with what I observed in the salon and the surrounding area. I used local trends, competitor activity and insights from other accounts to build a clearer picture of the customers each salon wanted to attract.

I asked owners where they wanted their businesses to be in two years, then translated the gap between their goals and current performance into a one-year strategy and practical actions. I used a simple planning sheet to track progress and met with clients at least monthly to review results and adjust priorities.

I turned those decisions into advertising: defining the target customer and offer, writing copy, shaping promotional packages and prices, and directing photography, model selection and styling. I also photographed and edited images myself. When needed, I brought owners and staff together to discuss the direction, helping align what the advertising promised with the experience customers would find at the salon. Working within a fixed advertising format, I chose each image, phrase and offer deliberately.

Advertising strategy for one salon

Situation

One salon was struggling to attract customers through its advertising despite having a distinctive identity and a clear vision from its owner. The advertising did not communicate what made the salon different from its competitors. Visits were inconsistent, the repeat-visit rate was low, and average customer spend was below the owner's goals.

What I did

I worked with the owner to understand the salon's direction and combined those conversations with local observations, competitor information and advertising performance data. This helped me identify a more specific target customer and clarify what the salon could offer that customer.

I changed the advertising to reflect the salon's identity more accurately. I gave greater prominence to an existing photograph that expressed the owner's vision, refined the model selection and visual direction, and wrote copy that communicated the salon's value without relying on exaggerated claims. I also raised the advertised coupon price rather than discounting it, aligning the offer with the customers we wanted to attract. To maintain consistency, I created a photographic style guide for the staff.

Result

Monthly visits attributed to the advertising more than tripled, the repeat-visit rate tripled, and average spend per visit rose by around 30%. Across my assigned area, average return on advertising spend rose from 1.1 to 1.4 during my time there. The salon owner later asked me to handle the advertising for his second location.

Read the article: The UX Lesson I Learned in a Quiet Tokyo Salon

Contact

I take on UX architecture and interface design, separately or together, depending on what the project needs. Hands-on engineering support is also available where needed. I work asynchronously by default and am used to working with teams across European time zones. If you have a new product or feature you want to build, or something you want to improve, a few lines about the work and where you need help are enough to start.

yoko@solastudio.studio

LinkedIn