Redesigning B2B Form Builder Platform

Higher adoption rates,
fewer support tickets, improved usability

Higher adoption rates, fewer support tickets, improved usability

Overview

Product Designer

Role

0+

Team Size

8 Months

Timeline

I redesigned an internal tool called Form Editor that allows different markets within the organisation to create and update forms tailored to their local needs. The initial version of the tool was created by a small group of developers, which led to an undefined product concept, non-intuitive flows, and terminology that was too technical for its intended users.

I redesigned the experience end‑to‑end, clarified the product concept, researched the target audience, improved the flows, refined the tone of the language, and made the interface more accessible to non‑technical users.

As a result, usability significantly improved: support tickets from markets to rollout managers decreased, and adoption increased as more markets began using the tool.

Project under NDA: This case study is based on my work on a B2B Form Editor internal tool. To respect confidentiality, all details are shared at a high level, and the visuals shown are taken from the internal product.


Desktop recommended: To enjoy the layout and visuals as intended, please view this portfolio in desktop mode.

Let's talk impact

• Reshaped the concept entirely to give the product a clear direction.

• Improved the platform’s information architecture, user flows, and overall usability, leading to higher adoption among internal teams.

• Developed documentation with clear guidance on how to use the tool and structure forms, and introduced a library of pre‑configured blocks that users can quickly apply when creating new forms.

• Local markets can now manage and update their forms independently, reducing reliance on rollout managers for routine changes. This has improved operational efficiency and lowered the number of support tickets.

The Challenge:
From Developer Built MVP
to User Centered Tool

The main challenges included:

  • Product concept

  • Identifying priority use cases

  • Technical language

  • Reconstructing an undocumented system

Step 1:
Building Foundational Understanding
& Defining the Product Strategy

When I took on the task of redesigning the internal tool, I quickly realized it was very different from the company's B2C website I already knew well. The original Form Editor MVP had been built by a small group of developers without design support and with minimal documentation. The existing documentation was highly technical and difficult to understand.

So my first step was to establish clarity:

Clear concept

The product lacked a clear definition of its intended use cases. While the concept was promising, we needed to articulate its purpose and ensure target users understood when and how to incorporate it into their workflows.

Interviews

I had interviews with the teams who will be using Form Editor to learn the team dynamics, and identify their needs. I learnt how markets create forms, documented their workflows and identified the touch points where we can support them.

Affinity Mapping

I captured interview insights on sticky notes and organized them into thematic clusters using affinity mapping.

Customer Journey

I mapped their customer journey, showing how touch points evolved before and after the redesign.

Existing Flows

To understand the status quo, I reviewed the Editor's existing flows, terminology, and interaction patterns. This helped determine the level of redesign effort required, including whether we could introduce custom components or needed to stay within the constraints of the core library.

Competitive Research

I also carried out benchmark research to understand how other products solve similar challenges.

Step 2:
Refining User Flows

I identified two primary flows in the product:

• Creating a form from scratch
• Editing existing form variants

I made a strategic decision to prioritize the editing flow. Since markets most often update forms they already have, focusing on this journey offered the greatest impact by reducing friction and improving efficiency.


I then designed the new flows, mapped all necessary states (empty, error, loading, etc.), and delivered the most critical ones within the limited project timeline. This led to an MVP that focused on the essential features required for the tool to be adopted and used consistently.

Creating a form from scratch flow

Redesign (on the left) and original MVP version (on the right)

Let's have a closer look:

Main screen

I redesigned the main screen so it now clearly presents all available actions within the Form Editor, giving users a complete overview of what they can do.

Setting up the form flow

I restructured the form‑creation flow so users first select the type of form they want to build, then land on the split‑view editing screen. From there, they can start adding elements and immediately see their changes reflected in the live preview.

Properties

I restructured technical properties and addable elements into well‑defined visual clusters, improving clarity and reducing the cognitive load during form setup.

Importing a form to edit flow

Redesign (on the left) and original MVP version (on the right)

Scannability

I refined the hover states and visual hierarchy to make the tree structure more scannable and easier to work with.

Split screen and live preview

The split screen divides the workspace into an editable panel and a live preview.


Previously, users had to edit the form, save it, and then click a separate button to open the preview in a side layer. Live editing wasn’t possible, which slowed down the workflow significantly.


The split screen not only enables real‑time updates as users modify the form, but also improves the tree structure’s scannability by preventing it from stretching across the full width of the screen.


Anatomy of
Tree structure element

Anatomy of Tree structure element

Redesign (on the left) and original MVP version (on the right)

For this project I had to redesign a component I never had experience before - tree structure.

Visual hierarchy and states

I introduced a visual hierarchy across all depth levels by making top‑level steps foldable and adding a left‑side indent for nested components based on their depth.


I introduced hover states, so all editing actions are displayed only on hover.


I removed the technical title within the tree structure.


The tree‑node component supported drag‑and‑drop, but it was not obvious. I added a drag‑handle icon, appearing on hover to the left side of each node, to make the functionality explicit. It also provides a clear visual cue for the hovered element, which is especially helpful when working with large, dense trees.


All of that improved the scannability of the tree structure, decluttered the interface, and removed unnecessary noise.

Hierarchy is indicated by the left indent. Step 4 is in a hover state, showcasing draggability and editing options. Step 2 is folded.

Tree structure UI

I redesigned the tree structure to follow established scannability and hierarchy practices.

The optimal height for a single branch (one row) in a dense tree is 36 px. Below 32 px, items become harder to scan and click; above 40 px, the layout wastes vertical space and reduces information density.

The ideal spacing between nodes is 10 px, which provides enough separation for visual clarity without breaking the rhythm of the hierarchy.

Step 3:
Post‑Redesign Evaluation
& Adoption Support

Example of guidelines for the markets.

Post‑launch user insights

I spoke with users to understand whether they were adopting the product after the redesign, observed how they interacted with it, and interviewed them. A key part of this research was assessing whether they could work with the technical language used in the app and understanding how technically savvy this user group actually is.

Drop in support requests

I spoke with stakeholders who confirmed that rollout managers began receiving fewer support tickets for minor tasks. Because this is an internal product, I don’t have statistical before‑and‑after data, but the feedback indicates that these types of tickets noticeably decreased in the months following the release of Form Editor.

Turning autonomy into consistency

Allowing markets more autonomy increased the need for guidance. I created detailed Confluence guidelines, standardized form setup, and introduced pre-configured building blocks for consistency. To boost adoption, I added direct links to these resources on the Editor’s front page for easy access.

Project Summary

Here’s a brief overview of the main challenges I encountered and how I addressed them:

The Challenge 

• Form Editor lacked a clear product concept and had no defined use cases. Although the idea was promising, we first needed to clarify its purpose and then prioritise the flows that required refinement. 

Impact 

• As a result, we defined the product’s purpose, its key use cases, and created a clear roadmap for which flows to refine first. 

• As an early MVP built with default components, the tool lacked refined interaction patterns, which resulted in highly unintuitive user flows. 

• I refined the flows using established interaction patterns and integrated components from the main website’s design library. Where necessary, I reworked existing components and introduced new ones, as in the case of tree‑structure component. 

• The product had almost no documentation or design library, which made onboarding and collaboration difficult. Critical knowledge lived only in code or in people’s heads, and there were no defined patterns, standards, or references for designers or developers. 

• Created foundational documentation and patterns by reverse‑engineering an undocumented system, giving teams a shared source of truth. 

• The product used overly technical language, making it difficult for our target teams to adopt it into their workflows. 

• We improved the language wherever possible, and for areas that couldn’t be simplified directly in the product, we created clear Confluence documentation to explain the terminology. As a result, markets were able to use the tool more confidently and more frequently. 

• The tree‑structure component lacked a defined visual hierarchy, resulting in poor scannability for users. 

• I redefined the tree‑structure component by introducing a clear hierarchy between depth levels, refining sizes and spacing, and optimising the visual system to improve scannability. 

Professional Growth

Professional UX, coding & interpersonal skills I developed during this project:

Prioritarisation

I learned how to prioritise what to tackle first when reworking an MVP, focusing on the changes that deliver the biggest usability improvements.

Concept definition

I realised how crucial it is to define the product concept early on. With a clear purpose and defined use cases, design decisions become strategic instead of reactive.

Understanding interconnected workflows

I focused on understanding the broader workflow ecosystem across teams, which enabled me to make design decisions with meaningful, cross‑team impact.

Designing a new component

I designed a new tree‑structure component, which gave me valuable hands‑on experience creating a completely new element from the ground up.

Next Steps

The next phase would be to focus on:

  • Validating the redesigned flows through usability testing, measuring adoption and usage across markets.


  • Introducing in‑product onboarding to reduce reliance on external documentation.


  • Improving the tool’s UI and microinteractions will help guide users more intuitively through their workflows.


  • Refine UI and interaction patterns for the tree-structure component.