Yap Labs
Nullius in verba
portfolio.jpg

Portfolio

I've been a designer, engineer, and product manager in one fashion or another for over 15 years.  This is a sampling of the projects I've worked on over the years.

HumanConcepts Suite


Company: HumanConcepts supports over 400 of the Fortune 500 companies with advanced organizational charts.

Solution: HumanConcepts Suite delivers the premier workforce planning solution to enterprises around the world.

Timeline: Jan 2011 - Mar 2012



Introduction

HumanConcepts supports over 400 of the Fortune 500 companies with advanced organizational charts. To accomplish this, HumanConcepts historically supported enterprise, Flash-based web, and desktop applications.

I was the lead designer on a major initiative to consolidate all of these into a unified software as a service (SaaS) solution, which leveraged the Silverlight platform. This decreased maintenance costs, expanded further into SMB markets, increased revenue with a subscription model, and substantially improved the customer experience. Ultimately, this helped solidify HumanConcepts as the de facto organizational chart standard by providing cutting-edge features in an interface easier to use than ever before.

In March 2012, Saba acquired HumanConcepts to expand its hold on the human capital management market. Here’s a quick introduction to what HumanConcepts as a product solves for enterprises.

I redesigned nearly the entire product during the consolidation process. I also had substantial input on the visual design and requirements along the way. Ultimately, the company saw over 65% year-over-year growth before being acquired by Saba.

This is a quick introduction to the product from 2011 / 2012, which represents the bulk of my contributions.

Methods Used

  • Heuristic analysis
  • SSNiF identification. This process was developed by Philip Haine to help focus designs by forcing every feature to be explained with a stakeholder and situation that informs the need (Stakeholder, Situation, Need, Feature). Ultimately, the needs become the primary focus of the design.
  • Wireframes
  • Low-fidelity mockups
  • Critical user stories

Quick introduction to some of the core features of the HumanConcepts Suite

Example Problem: Managing charts for every solution

Enterprise customers using the previous HumanConcepts solution (OrgPlus) created numerous charts for every possible situation. For instance, a single manager might need different charts to review quarterly budgets, annual budgets, annual employee reviews and position vacancies. This complicated maintenance with duplicated efforts for each chart, which made it difficult to readily answer critical questions or make informed decisions. This also substantially increased the learning curve to use or create charts, because each chart independently defined style, color and organization of basic demographic information.

To further complicate matters, charts used on the web-based enterprise product had to be created in a relatively out of date Windows desktop app. This application was designed by marketing and engineering without any professional UX designer; and therefore, had some pretty funky workflows.

Solution: Make chart data far more flexible

To solve these problems, we redesigned HumanConcepts (flagship product) to give chart consumers the ability to show and hide collections of data. By simply checking and unchecking boxes in the chart legend, a manager can change the duration of information shown (year to date, quarter, etc.), types of information highlighted, or even positions shown in the chart. So, switching between budget highlights and annual review highlights might be as simple as checking a box. Field options can be toggled on/off to show and hide different collections fields (raw or calculated). Each view is a different chart with different data, representations, etc. So, with a handful of views (e.g., salary, planning, performance, etc.) and several field options in each view, hundreds of charts can be represented. This dramatically simplifies maintenance of charts, the experience of the manager, and dynamic comparison of disparate data.

Views can also be scoped to specific roles or groups of users based on permissions or position within the org chart. The data is also filtered and secured on a per field basis by both role and position in the organization (e.g., managers can only see subordinate salaries). This complex security policy protects data and allows a single chart to be used by many different people… even different roles in some cases (e.g., contact information and pictures).

I also simplified the expression of chart design, so a single chart is more easily reused. Organizations that previously required dozens, even hundreds, of charts to support the combinatoric conditions, may now use a handful charts and get even more insight by comparing and analyzing data in new ways without massive effort building new charts.

While chart design previously involved an interface only decipherable by a select few “chart lady’s,” the new design is fairly intuitive. Anybody well steeped in the HR world can get the basics in a few minutes, and pick up many of the more powerful concepts within a few hours.

Finally, we added the ability to compare two different charts. This allows comparing different views of data. For instance, comparing a performance and salary view may help a manager decide who should be promoted or allocated an additional bonus. This also allows comparing different time periods, which shows how an organization evolves over time. This is hugely beneficial in many circumstances. There were several key clients going through major, international re-orgs that identified this one feature as saving huge amounts of time and reducing risk throughout the project.

Results

Powerful, but simple chart creation. Many success stories are driven by these powerful charts.
Easy domain management, even across different ERPs. For instance, a North America domain on Oracle can be reconciled with a Europe domain on SAP, which is hugely powerful.
Flexible end-user experience that removes complex components from the interface for simple use-cases. However, progressively exposes functionality to power-users (typically HR professionals).

Conclusions

I spent over a year on this project, and touched nearly every piece of the HumanConcepts offering along the way. There were a couple contractors that helped with the visual design, but I designed the vast majority of the product IXD. The rest of the product team and engineering teams were absolutely critical to my success. Without them, I wouldn’t have been able to get access to the subject matter expertise necessary to grok such a deceptively complex industry and solve these problems (and many, many more).