Signature 0→1 product case study · ten-week solo ownership
Designing a single mobile home for deskless communication, learning and growth.
dnata needed a brand-new internal platform that could reach operational employees beyond the desktop. I designed DC Connect from zero to one: secure onboarding and account recovery, a communication hub, news and notifications, microlearning, course progress, achievements and employee profile services—all within one coherent mobile product.
Select the product board to inspect the supplied interface evidence.
From product definition through engineering handoff
End-to-end product design ownership
Access, communications, learning and performance
High-fidelity screens and interaction variants represented
Section 1 of 11Overview
Overview
A new employee product, not another isolated internal tool.
DC Connect was designed as an employee-facing platform for dnata operations. The product brings communication, learning, account services and personal development into one mobile experience, giving deskless staff a consistent point of access instead of requiring them to move between separate systems and channels.
Unify the employee digital experience
Provide a recognisable home for company news, timely notifications, learning content, performance visibility and account management.
Build around four stable destinations
Home, News, Learning and Profile establish a simple mental model while supporting deeper workflows within each area.
The original discovery repository and measurement plan were not retained. Discovery is reconstructed from the shipped interface, the ten-week context and remembered product goals; exact participant counts, quotations and impact percentages are intentionally omitted.
Employee needs were experienced as separate touchpoints.
- Communication, learning and account support lacked one recognisable destination.
- Employees had to know where to go before completing a task.
- Access failure or missing content risked becoming a support request.
- Learning progress was disconnected from the wider employee experience.
One mobile relationship organised around employee intent.
- A secure gateway resolves sign-in, registration and recovery.
- Four persistent destinations establish a stable mental model.
- News, notifications and learning use shared hierarchy and states.
- Profile and performance make continued participation visible.
Context
Deskless communication fails when access, relevance and follow-through are separate problems.
Operational employees need information while moving between shifts, locations and responsibilities. A useful internal platform therefore had to do more than publish announcements: it needed to make access recoverable, prioritise timely content, support short learning sessions and return a visible sense of progress.
Access without support dependency
Sign-in, registration, verification and account recovery needed to work as complete self-service journeys.
Hierarchy instead of communication volume
Employees needed to distinguish latest news, direct notifications and broader content without treating every update as equally urgent.
Learning shaped around operational rhythms
Discovery, active learning, completion and offline access had to remain usable in short, interruptible mobile sessions.
Progress that feels personal and actionable
Performance, achievements and settings needed to reinforce value without becoming a dense analytics dashboard.
The strategic shift was from “send employees information” to give every employee a reliable digital home.
Role
I owned the product-design path from an open brief to engineering-ready flows.
As the solo product designer, I was responsible for framing the product, defining the interaction architecture, designing the high-fidelity system, covering core and recovery states, and preparing the design for engineering implementation within ten weeks.
Product and experience definition
Scope, journey architecture, navigation, interaction patterns, visual system and end-to-end high-fidelity flows.
Engineering-ready product design
Reusable components, responsive mobile layouts, interaction states, empty states, recovery paths and annotated specifications.
Feasibility and implementation
Engineering reviews, behaviour clarification, implementation questions and continuity through development.
Mobile first
Primary journeys had to remain legible and operable on a narrow handheld screen.
Secure identity
Account access needed clear verification, password and recovery safeguards.
Broad workforce
The interface needed plain language, recognisable patterns and low training dependency.
Ten weeks
The design had to create a coherent MVP foundation rather than perfect every future service.
A complete employee relationship
- Sign-in, registration, OTP verification and account recovery
- Home, search, news, article detail and notifications
- Course discovery, progress, content, reviews and offline states
- Performance, achievements, profile media and account settings
- Reusable navigation, cards, fields, progress and empty states
Expansion without destabilising the foundation
- Additional service modules beyond the four-pillar model
- Advanced workforce analytics and manager dashboards
- Deep behavioural personalisation
- Complex social or community mechanics
- Organisation-wide instrumentation pending launch governance
Discovery
The missing research record is rebuilt as decision evidence—not invented user testimony.
The delivered interface reveals the questions the product had to answer. I reconstructed the discovery model around user context, task criticality, information priority and technical dependency. This preserves the strategic reasoning without claiming participant numbers or quotes that cannot be verified.
Context mapping
Identify where employees encounter updates, learning needs and account problems during operational work.
Task hierarchy
Separate frequent tasks such as reading news from high-risk but occasional tasks such as account recovery.
Content and service inventory
Group communication, learning, performance and settings into a scalable product architecture.
Constraint mapping
Design for narrow screens, interruption, varied digital confidence, security and future expansion.
Behavioural needs inferred from the delivered product
Recover without escalation
Employees should register, verify and recover access through clear sequential steps without relying on memory or support.
Know what matters now
Home and notifications should separate new, recent and evergreen content so urgency remains meaningful.
Resume learning quickly
The product should preserve active-course context, show module progress and support short or offline sessions.
See progress without interpretation
Performance and achievements should communicate completion, momentum and next actions through plain summaries.
Product reasoning remained visible from context to interface.
Define
Reframe DC Connect as a four-pillar employee platform.
The design needed a simple organising model that employees could learn once and reuse. The bottom navigation therefore concentrates the product into four persistent destinations while authentication remains a separate gateway.
How might we give deskless employees one secure and intuitive mobile destination for staying informed, learning and understanding their progress?
Employees should gain or recover access, identify important updates, discover or resume learning and understand personal progress without extensive training or separate systems.
Design principles
Recognition over recall
Use familiar mobile patterns, visible status and descriptive labels.
One clear next action
Make Next, Verify, Start Learning or Resume immediately identifiable.
Short sessions, persistent progress
Preserve context through interruption across learning and communication.
Recovery is a first-class journey
Guide users forward from identity failure, empty states and unfinished work.
Motivation without noise
Use achievement and progress signals without overpowering operational content.
A foundation for future services
Make navigation, components and states reusable beyond the initial MVP.
Success measures defined for launch
These are the measures the product should have been instrumented to capture—not retroactively claimed results.
Reach first value
Registration completion, verification success, time to first session and recovery completion.
Reach and relevance
News opens, notification reads, article completion and repeat visits.
Continue and complete
Course starts, resume rate, module completion, offline use and abandonment.
Reduce support dependency
Access contacts, failed recovery attempts and repeated reset requests.
Perceived usefulness
Ease of use, confidence in updates, satisfaction and return intent.
Architecture
Four destinations create a stable mental model across a broad internal ecosystem.
The architecture gives each employee question a predictable home: What is happening? What should I know? What can I learn? How am I progressing?
Home
Latest information, popular courses, search and a concise overview of the wider platform.
News
Featured stories, categories, article detail, reactions and time-to-read signals.
Learning
Course discovery, active and completed learning, modules, reviews and offline support.
Profile
Performance, achievements, settings, identity preferences, accessibility and language.
Access sits before the product—not inside one destination.
Sign-in, registration, verification and recovery establish trust before employees enter the four-pillar product model.
Design system
A lightweight design system made a broad MVP feel like one product.
A consistent blue-led interface, generous white space, repeated action hierarchy and restrained use of illustration allowed security, content and learning screens to share one visual language.
Persistent destinations
Home, News, Learning and Profile repeat across the product and expose active state clearly.
One primary hierarchy
Primary, secondary and passive actions use consistent prominence across identity and learning.
Reusable cards and metadata
News and courses share scan-friendly patterns without losing their distinct information needs.
States are product content
Verification, success, empty, locked, offline and recovery states explain status and next action.
Continuity across sessions
Tabs, completion marks and resume actions preserve context through interruption.
Blue-led, calm and recognisable
Generous white space, restrained illustration and consistent typography connect broad workflows.
Key journeys
The delivered product covers the entire employee relationship—from first access to continued development.
Each journey addresses a different risk: access failure, missed communication, learning abandonment or unclear personal progress.
Secure entry, registration and account recovery
The identity journey begins with email lookup and supports existing users, new-account creation, social sign-in, OTP verification and password recovery. Each state isolates one decision and makes recovery visible.
Discovery and urgency are different product jobs
Home provides breadth, News supports browsing and deeper reading, and Notifications separates new and previous activity. This prevents the platform from becoming one undifferentiated feed.
A complete mobile-learning lifecycle
Learning spans category discovery, filtering, active and completed courses, course detail, module progress, video and theory content, ratings, reviews, empty results and offline download.
Progress, achievements and personal settings
The profile area brings together learning performance, achievements, weekly patterns and account controls. Avatar selection and cropping make the account feel personal without complicating essential settings.
Delivery
The final two weeks converted a polished concept into an implementable product system.
The exact historical sprint log was not retained, so the timeline below reconstructs the project cadence from the ten-week duration and delivered scope. The handoff focused on behaviour and reusable states—not only static frames.
Frame the product
Clarify the employee problem, identify core services, establish MVP boundaries and map product risks.
Build the architecture
Organise identity, communication, learning and profile into a stable navigation and task model.
Resolve end-to-end flows
Create high-fidelity journeys including recovery, empty, completion and modal states.
Prepare implementation
Consolidate components, document behaviour, review feasibility and support handoff.
Flow-level specifications
Entry points, transitions, validation, resend behaviour, success states and destinations.
Reusable component states
Buttons, fields, tabs, cards, navigation, progress, modals and empty-state patterns.
Engineering clarification
Reviews to resolve implementation questions and protect interaction consistency.
Product risks addressed before handoff
Account dead ends
Explicit email resolution, OTP resend, password criteria and recovery success.
Information overload
Separate Home, News and Notifications with category, time and hierarchy cues.
Interrupted learning
Active-course state, completion, resume actions and offline download.
Unavailable content
Illustrated empty states, explanatory copy and constructive next actions.
System inconsistency
Repeated navigation, field, button, card, tab and status patterns.
Unmeasured adoption
Prospective activation, communication, learning, self-service and trust measures.
Outcomes
The breakthrough was a unified platform foundation—not an unsupported percentage.
DC Connect was delivered to engineering, developed and shipped. The product established a single employee-facing system for communication, learning, identity and progress. Quantitative adoption, engagement and organisational-performance data were not retained for this portfolio reconstruction.
New product shipped
The work moved from an open opportunity to a complete mobile platform delivered for implementation.
Verified project outcome.Employee needs unified
Identity, communication, learning and progress share one navigation and interaction model.
Qualitative outcome supported by the shipped scope.A scalable ecosystem
The architecture supports future services without forcing employees to relearn the product.
Strategic outcome inferred from the modular architecture.End-to-end ownership
The solo engagement demonstrates breadth management and implementation-oriented judgement.
Verified duration and ownership.Verified delivery evidence
- Ten-week project
- Solo product-design ownership
- Delivered to engineering
- Developed and shipped
- Frames cover identity, communication, learning and profile
Missing outcome evidence
- Original participant methods and quotations
- Stakeholder and cross-functional team details
- Launch date and active-user measures
- Communication reach and acknowledgement
- Learning completion, satisfaction and support-volume change
Recommended validation if the product is revisited
| Journey | Representative task | Primary signal | Key risk |
|---|---|---|---|
| Identity | Recover an account after forgetting the password. | Completion, time and support requests | OTP or password-rule confusion |
| Communication | Find and read a recent operational update. | Findability and comprehension | News versus notification ambiguity |
| Learning | Resume an active course and complete the next lesson. | Resume success and abandonment | Loss of progress or module context |
| Profile | Review performance and change a notification preference. | Interpretation and settings success | Analytics density or hidden controls |
| Accessibility | Complete core journeys with text scaling and assistive technology. | Completion parity and issue severity | Contrast, focus order and touch targets |
Reflection
The most important decision was to design the relationship between services—not just each service.
DC Connect could easily have become a collection of attractive mobile screens. The product became coherent because identity, communication, learning and performance were organised around one stable mental model and repeated interaction system.
Recovery defines trust
A workplace product is useful only when account failure and incomplete tasks provide a reliable route forward.
Mobile breadth requires ruthless hierarchy
Four destinations, visible primary actions and progressive disclosure made a broad platform navigable on a narrow screen.
Systems thinking accelerates handoff
Reusable patterns reduced inconsistency and gave engineering a clearer implementation model.
The project shifted internal communication from a set of touchpoints into a product employees could return to, learn and grow through.
Need a guided walkthrough of the work and decision-making?
Start a conversation