Corderum Research

Phase 1
Needs Gathering

Imagine this, you are working with a client on a new idea while conducting a design thinking "needs gathering" exercise. Midway through the exercise, a new unrelated theme keeps surfacing. What do you do?

We ended up shelving the original project and pivoted on a new set of problems and solutions that would become Corderum. Once we decided to pivot we were able to focus on three primary struggles:



1 Subscription Management

As a financial manager, we need to know:

  1. What applications we are paying for?

  2. When are they up for renewal?

  3. How are they being expensed and to whom?

  4. What are the terms?

  5. Are they being utilized?

  6. Have they been shelved? 


2 Policy Management and Governance

As a CIO, I need to:

  1. Make onboarding and offboarding instant, easy and secure.

  2. Create subscription distribution decisions by company, org, role, or individuals.

  3. Be able to quickly and easily change permission types.

  4. Protect company IP by knowing:

    1. what environments have been created?

    2. who has access to them?

    3. and how are they protected?

  5. Be able to monitor usage and identify individuals that need more training.


3 Cloud Migration

As a CTO and BizOps, we need to:

  1. Reduce the time and complexity to fire up new environments.
    From weeks to minutes.

  2. Not overspend and be able to get maximum utilization out of our systems.

  3. Understand what we are paying for and how we get billed?

  4. We need to cloudify our internal systems.

  5. We need to monitor systems and reallocate resources to meet demands.

  6. We need to make sure all systems secure our IP


In the Mural below you can see some of the results of these initial meetings.

Seen on the right side of the Mural is when we too a second pass with more technical members of the team

Phase 2
Journey/Empathy Mapping

In this second phase, we were getting a better idea of who our personas were and we started plotting their journeys.
These journey maps later evolved into flow diagrams.

Side Note*  Over the years of doing this type of research, I found that there is a lot of overlap between creating empathy diagramsjourney maps, and even persona development. For this reason, I like to combine these exercises and diagrams into a single journey map artifact. 

Figma logo.png

Phase 3
The Competitive Analysis

After conducting over 30 customer sessions the results were the same; each participant one by one validated the need for subscription management, policy management, and cloud migration. Some of them were already holding internal meetings to discuss how they might tackle these problems within their own organizations. 

Obviously, there must be other companies out there working on similar solutions. Though it was surprisingly difficult to find some of these companies we ended up with more than 15 viable competitors. 

At the request of some potential investors, we were tasked with presenting our competitive analysis. We started with a very organized and categorized spreadsheet that over time started to become overwhelming and unreadable. To remedy this eyesore I decided to use some of my dashboard components to create an interactive prototype to make it easy to filter and visualize the competitive analysis.

Figma logo.png

Phase 4
Ideate, Design, and prototype