Research & Analysis

Before moving into high-fidelity design, I mapped the full dependency structure between enrolment types, modules, and user actions.

This helped define the universal logic that would let the same flow handle B2C, B2B, and Coach enrolments without breaking. The following are the main connections I found from studying the manual enrolment.

Customer type ↔ Enrolment modules

Each type (B2C, B2B, Coach) triggered different modules and default tags.

Customer type ↔ Enrolment modules

Each type (B2C, B2B, Coach) triggered different modules and default tags.

Customer type ↔ Enrolment modules

Each type (B2C, B2B, Coach) triggered different modules and default tags.

Payment logic ↔ Content access

Price, discounts, and payment mode determined which content modules were automatically unlocked.

Payment logic ↔ Content access

Price, discounts, and payment mode determined which content modules were automatically unlocked.

Payment logic ↔ Content access

Price, discounts, and payment mode determined which content modules were automatically unlocked.

Timezone ↔ Pod formation

Timezones and participant caps directly affected how user groups (“pods”) could be created and scheduled.

Timezone ↔ Pod formation

Timezones and participant caps directly affected how user groups (“pods”) could be created and scheduled.

Timezone ↔ Pod formation

Timezones and participant caps directly affected how user groups (“pods”) could be created and scheduled.

Start date ↔ Communication templates

Enrolment start dates dictated which automated emails and sequences were triggered.

Start date ↔ Communication templates

Enrolment start dates dictated which automated emails and sequences were triggered.

Start date ↔ Communication templates

Enrolment start dates dictated which automated emails and sequences were triggered.

Coach assignment ↔ Email visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Coach assignment ↔ Email visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Coach assignment ↔ Email visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Enrolment status ↔ Dashboard visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Enrolment status ↔ Dashboard visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Enrolment status ↔ Dashboard visibility

Coaches were optionally included in B2B email flows depending on their group linkage.

Scope Definition

Scope Creep
Important Insight

After the research and architecture stages, it became clear that to make the enrolment process consistent across all programs and client types, we needed to create a universal Form Builder.

Once I fully understood the business logic, I broke it down into modules and mapped the relationships between them. The following diagram shows how different form modules can influence or disable each other. With this foundation in place, I was able to design both the Form Builder and the enrollment form itself.

Form builder combinations

I combined all the modules and tested their interactions against existing use cases. This stage helped surface and resolve unforeseen edge cases. Together with my product manager, I conducted several interviews with Customer Success specialists using simple linear click-through prototypes.

I combined all the modules and tested their interactions against existing use cases. This stage helped surface and resolve unforeseen edge cases. Together with my product manager, I conducted several interviews with Customer Success specialists using simple linear click-through prototypes.

On the left of the demo you can see a piece of the admin UI with form settings.

On the right you can see how the Client side responds to every change. Every possible combination is accounted for.

“Building our automated enrollment flow was a turning point. We learned a lot from the process, and it opened up an entirely new source of revenue that simply wasn’t possible before.”

Key Lukin

Head of Product | Positive Intelligence

Head of Product Positive Intelligence

Conclusion

The new automated enrollment flow eliminated bottlenecks in purchasing programs for small and mid-sized teams, making it faster and easier to get started. By balancing automation with flexibility, the solution unlocked new revenue streams, reduced manual overhead, and improved the overall customer experience. This project clearly demonstrated how thoughtful system design can directly drive growth and scalability.

Thank you for your attention.

Dmitri Tonitsoi

2021-2025 Lead Designer | Positive Intelligence

2021-2025 Lead Designer

Positive Intelligence

© 2025 Dmitri Tonitsoi

© 2025 Dmitri Tonitsoi

© 2025 Dmitri Tonitsoi