Michael Tseng | User Experience Designer
logo_powerforward.png

PowerForward

 

 Impactful Leadership Development

How to Create a Leadership Training Module?

 
I don’t look at myself as a basketball coach. I look at myself as a leader who happens to coach basketball.
— Mike Krzyzewski, "Coach K", Duke University Basketball Coach

 
 

Brief

PowerForward is a web-based app that helps businesses build team synergy and help individuals develop leadership skills based on Coach K’s philosophies and methodologies.  Michael William Krzyzewski, also known as “Coach K”, is the all-time-winningest men's college basketball coach, developing hundreds of college and professional players over the last four decades, resulting in five NCAA Men's Div I BasketBall Championships and three Olympic gold medals.  Built on the winning track record of Coach K, PowerForward takes his approach and uses the coach's keywords for success as a foundation for an impactful leadership and team development program.

Role
I worked as the sole Product Designer committed to improving the overall user experience as well as exploring new features enhancing the platform's value.  I was responsible for and led the design from whiteboard brainstorms, paper/lo-fi prototypes, to high-fidelity screens.  Extensive user research and testing also played a significant role as I wanted to ensure the product was as user-centric as possible.  Outside of handling UX and design, I also wore the hats of a project manager and QA as we were an extremely lean team.

Time Frame
6 months

 
 

First Things First…

One of the first things I wanted to establish was a style guide and giving our marketing site and platform a clear visual hierarchy. We wanted our primary color scheme to have some recognition to Duke University’s basketball team colors while at the same time providing enough identity for people to start recognizing PowerForward as its own brand.

PF_StyleGuide.png
PF_MarketingSite.png

A Strong Foundation

Before building and finessing the content portion of the platform, I wanted to make sure that the flow of the product made sense to our users.  One major issue I've encountered was the user creation process.  We were relying solely on a reset password token to create the user's initial password.  This caused a great deal of headache as our invite link would "expire" once its clicked, regardless if they finish creating their account or not.  Working closely with our dev team, I suggested a much cleaner flow for on-boarding new users.

New features were also added for our admin portal as well.  We ultimately wanted a much easier process creating new accounts and capturing usage data on our user base.  Eventually, we would also add an automated email system alerting our users of any newly released content.  Having a more robust admin portal allowed us to better service our users.

 
PF_AccountCreation1.png
PF_AccountCreation2.png
PF_AdminFlow.png
 

Personas & Journeys

Before tackling the product itself, understanding our user base through personas is important as it paints a clearer picture of who our users are, what we are building, and the “why” we are building it for them. It also helps us visualize and humanize the project as well, putting a human face behind numbers and statistics.

 
PF_coachingpersona.png
 
PF_UserJourney.png
 
 

From Users to Leaders

User feedback is crucial, especially when a product is new.  It is that feedback loop that allows us to learn firsthand what our users need the most.  We were fortunate enough to have a large group in our pilot program to collect data from.  I led in-depth interviews with our power users as well as users that have dropped off in usage to better understand their pain points and what led to that drop off.  I also collected data from surveys to validate some findings as well as planning for future features and iterations, especially on how to make our content and lesson structure more relevant and “sticky”.

 
pic_1.jpg
pic_2.jpg
pic_3.jpg
pic_4.jpg
 

Usage Habits

By understanding current usage habits and pain points our users faced, I set out to design a more efficient user flow.  This would help our users maximize their time in our platform, and help dictate what content we would be pushing and showcasing.

We changed various features within our platform as well.  There were certain areas simply not being utilized and from the feedback collected, I was able to offer more engaging features such as goal setting and a lesson directory.  Our lesson structure was revamped as a result of this - moving from a bi-weekly release to monthly.  This gave our users more time to consume and discuss the content amongst their peers and team members.

PF_UserFlow.png

Wireframes

In order to give our platform a facelift, I started testing with simple paper prototypes validating certain features ensuring it is what our users wanted and needed.  I later moved to lo-fidelity wireframes to get a better feel of the site's final layout before moving into the high-fidelity versions.  Testing was done at every iteration - I would much rather make small minute changes now rather than large time-consuming ones later on.

The design gave our app a much cleaner and modern look, with easy access to functions and features our users needed.  It also gave us more control directing our users in the site resulting in less dead ends.

 
PF_wireframes_lofi.png
PF_Redesign.png
PF_Experience.png
 

Future Plans…

I've also started laying down the groundwork for a new feature in our app, allowing our users to be connected with a coach.  This creates a much more engaging experience - most importantly giving our users some sort of accountability as they progress through their lesson plans.

 
whycoaching.jpg
automatedgoals.jpg
workingwithacoach.jpg