Solving problems - from a design perspective
Before starting Preact, I consulted for a large web company on a project where I built wireframes and created concept visual designs for a new product they were going to be releasing. One of my favorite parts about that job was the fact that I wasnât limited by specs and requirements, and that I had the freedom to let my imagination run wild. I could ask myself the question, âWhat kind of information would I find useful to complete X if I were on this page?â I remember putting the development teams through their paces as they scrambled to find out if they were technically able to pull some of the associated data that I wanted to use and display.
The thing that really drove me back then was the ability to take a simple concept and bring a new perspective to it - one that wasnât limited by constraints or technical limitations. Instead, I had the opportunity to ask, âWouldnât it be cool/useful/awesome if we could ______?â, and then explore that possibility.
Ever since starting Preact, this has been one of the main focuses of my job. And itâs really what our customers are looking for when deciding on a customer success platform. The underlying question is, âCan I use this customer success platform to make a difference in my bottom line and in how I communicate with and understand my customers?â
Anyone can collect customer data and regurgitate it to you; that part is easy. The thing we focus on at Preact is answering the question, âWhat does this mean, how can we present this information that makes sense, and how can we make it actionable to the type of person looking at this data?â We have the unique challenge of creating actionable insights for C-levels, account manager, sales teams, support and success representatives, and product teams - all in the same product. As a result, the challenge is much larger. But thatâs what makes it exciting.
As an example, I thought Iâd show some of the work that led up to our most recent version of Preact Sidebar, our portal to presenting customer activity.
In a very early version, we focused very heavily on visual events. And of course, customer activity timelines look great when they're full of pictures, but you have to make it work when it's full of other types of data.
Another iteration showed summaries of types of events. Maybe interesting. But useful? Not really.
Or what if we tried to come to conclusions about users that would help our customers make more informed decisions? The mockup below, for example, pointed out why this user was important and highlight trends that made them differ from the average user. This information can come in handy when communicating with them. (Are they a novice or a computer wiz?)
We condensed into more of a sidebar timeline and came up with something like this, trying to only highlight events that are relevant to you as a user.
If you were an account manager, you might see this screen that included some high-level stats.
Or we could throw a bunch of unique charts and graphs on the page.
Or what if we broke things down into sessions and highlighted important events in sessions?
Or maybe we can find a happy medium between charts, insights, and stats.
None of these are what we have in production today, and are miles behind what we are working on now. But I hope this gives a little insight into how we build product. And when you're creating something no one has ever built before, the challenge is that much greater. There are no competitors to copy, and no ideas to steal.
Preact has the very unique opportunity to make sense of loads of customer data. If we simply regurgitate collected data onto a page, there's nothing exciting about what we do. But when we start asking questions like, "What does this data mean?", "How does their activity correlate with other events?", and "What kinds of patterns can we discover that make a significant impact in the long-term value of this customer?", then we can start to find and present relevant insights that our customers have come to rely on us for today. And we're just getting started.
Cory Watilo Co-Founder @watilo









