BETA

INTRO

BETA

WHAT IS A UX-STRATEGY• Communicates an overarching approach, vision or big idea that serves as a

„North Star“ of UX

• Aligns user experience design with business strategy

• Differentiate a company‘s product and services from those of its main competitors

• It describes prioritized customer segments, and how to address their needs, wants, and interactive behaviors

• Provides a road map that shows how future releases progressively achieve high-level goals

BETA

BUSINESS STRATEGY ALIGNMENT

„Like analytics, UX is a an area in which we want to excel. Considering that we are targeting non-technical users, the feel, visual design, intuitiveness and overall experience will impact the rate at which we convert customers, get them productive quickly and retain them. Considering that many competitors experiences have a very logical/

technical/almost antiseptic feel to them, our approach can yield a much more emotional experience if done well, and can be a second area of competitive differentiation.“

read more here...

BETA

CUSTOMER NEEDS (WIP)BETA

SPECTRUM OF THE GETCOURSE USER EXPERIENCE

BETA

GETCOURSE UX - PRINCIPLESOur applications should provide instant value by being simple, consistent, personal and

accessible

simple consistent personal accessible

BETA

simple ?

Simple means “having few parts; not complex or complicated or involved;”. Our Applications are simple by:

• Single purpose interfaces

• Smooth user guidance

• Clear call to action

• Easy to learn

• Error prevention

• Do not let the user guess whats happening (feedback)

BETA

consistent ?

Consistency means “logical coherence and accordance”. Our Applications are consistent in:

• Elements

• Design

• Content

• Interaction

BETA

personal ?

Personal means “to be particular to a given individual”. Our Applications arepersonal by:

• allowing a private experience

• allowing to customize the look and feel

BETA

accessible ?

Accessible means “capable of being reached”. Our Applications areaccessible by:

• offering access on major devices

• offering keyboard shortcuts

• offering simple controls

• being simple

BETA

NEXT STEPSWE ARE ALMOST THERE

BETA

Phase 1GET READY

Phase 2OPTIMIZE

Phase 3 SPREAD

Phase 4 REDUCE

BETA

Phase 1

1. Repair build-measure learn loop, by measuring key metrics

2. Remove code duplication, establish shared ui library

3. Bring feature flagging to production

BETA

Phase 1• integrate mixpanel in all applications

• define actionable metrics

• start analyzing the funnel

• unify used base classes with shared ui-library

• deploy feature flagging application and connect it to the frontend implementation

BETA

Phase 2

1. Optimize user-flow along the funnel (signup, course creation, invite)

2. Optimize first usage experience (onboarding)

3. Optimize feedback, error-handling along the funnel

BETA

Phase 2• remove course creation from signup process

• allow users to signup via google or facebook

• use no-slides area in the editor to show big buttons, that helps to add slides more quickly

• optimize invitation by providing and long-lasting link that can be used in various mailing-tools

• reduce rich-text possibilities

• use intro.js for first-run experience optimization

• adjust error handling & input validation

• provide consistent feedback (system state)

• adjust error prevention, exclude impossible or unwanted user paths (disable buttons in different states, hiding things that aren‘t possible)

BETA

Phase 3

1. Mobile support for consumer application

2. Optimize domainadmin application for a high volume of users and courses

3. Optimize performance (speed)

BETA

Phase 3• introduce search, filter, pagination (endless scroll) for all

lists in the domainadmin application

• optimize ui to cope with big lists (think of email-clients and the likes) - so we can handle big amounts of users and courses

• introduce categories or tags for courses

• optimize consumer application for mobile usage phone, tablets and than desktop

• optimize frontend performance by reducing loading time or bootstrap models by the backend

• use CDN to deliver application assets

• optimize backend performance by using better servicelocator workaround and the likes

BETA

Phase 4

1. Eliminate unneeded features2. Reduce code by further de-

duplication and abstraction

BETA

Phase 4• figure out which features aren‘t core functionality or

are not used by the addressed customer segments and remove them from the code base

• optimize code base along identified core functionalities

•

BETA

GETCOURSE UX PROCESS SUGGESTION

Idea

CodeData

Learn Build

Measure

BETA

BETA

Requ

irem

ent

Idea

Build

Dep

loym

ent

Measure

Code

Kick-off Brainstor-ming

1st Design/Scribble/Wireframe

Imple- mentation

UX-Prototype

DesignBusiness

Technology

BETA

Dep

loym

ent

Code

Measure

Tim

eout

Learn

Data

Run previous defined experiment over a limited time period. Collecting data regarding predefined metrics.

AARRR METRICS

Acquisition - users come to the site; you have their attention

Activation - user performs some key activity that indicates a good first visit

Retention - user continues to do that key activity indicating they like your product

Referral - user gets other users to join

BETA

BETA

Analy

ze

Data

Learn

Requ

irem

ents

Build

Idea

Conclusion Select next learning goal

Define Experiment

find most simple way

to learnDesignBusiness

Technology