Solving Problems For the Right Beneficiary

As a product manager, your job is to identify problems to solve, do some prioritization, and ensure that you solve them as fully as possible, given the resources and constraints of your organization.  (To be super explicit: the best solutions aren't necessarily delivered as new features.)

In enterprise product management, you often have multiple constituencies that you need to solve for.  Attention must be paid to all of them to keep both customers and the team happy.  In my mind, when you're choosing problems to work on, you should be explicit about whose problem you're solving.  I use the term "beneficiary" to denote for whom or for what I'm solving for.  Here are the most common beneficiaries:

* The user. 

The user is an individual human.  In consumer, the user is the customer and is the only thing that matters.  In enterprise, there are often many different kinds of users - some users aren't even end users of your product: they're administrators or finance folks.  Even within end users, there can be many different kinds of users.  Some delineations are: novice and expert users of your product, end users with different job roles or responsibilities, or folks in different geographies that have different contexts and capabilities (iOS versus Android, slow connections versus fast connections, etc.)  

If you have different kinds of end users, the best way to have a quick way to be specific about who you're solving for is to go through a persona exercise.  Individual (and team) personas can be incredibly helpful to make sure that you can shorthand a set of motivations, problems, capabilities, and limitations for end users.

* The customer.

Again, in consumer, the user is the customer - the person who pays.  In enterprise, the customer can be one of many folks: an IC putting down a credit card, a manager authorizing a purchase, a procurement department that will "right size" the offering to be bought.

At scale, if the person paying isn't the person using the product, you're going to have to do affirmative work to prove to the purse-strings-holder that you're delivering value commensurate with the price being paid.  Fun note: this work often helps lead to step-function expansions in deal size.

* The system.

Sometimes you're going to solve a problem that makes your system more reliable, available, resilient, or performant.  For example, work that makes it easier to scale (either horizontally or vertically, your choice) or lets you increase placement (standing up an EU region is the most common example for US-based startups targeting EU-based customers) has "the system" as the beneficiary.  To draw a line in the sand, this work will have no user-facing changes in the experience of a working application (with the exception of decreasing latency).  Solving for the system is also different than solving for...

* The team.

Sometimes you will solve a problem that is borne by your internal team - perhaps your developers, your sales team, your support team, or any collection of groups of folks inside the organization.  Solutions often end up automating manual processes or making it easier to make changes to the product.  Solutions can include everything from new ticketing systems, string repositories, cron jobs, documentation, full on code reorganizations, and just hiring a bunch more people.

* The business.

Lastly, problems that are borne by the business are generally problems where the outcome is either "increase revenue" or "reduce costs".  These are where the value you are creating is almost entirely captured by the business that offers the solution.  Being intentional about pricing and packaging helps immensely on the revenue side; sadly, there are often no real alternatives to large infrastructure projects to make reductions on the cost of goods sold (COGS) side.  

You may also find that there are other classes of beneficiaries that your organization needs to consider - that's fine!  Being clear and up front about which beneficiaries you are serving will allow you to make much better prioritization and sizing decisions as a product lead.

Product Management Is Not Just About Creating Value, It's About Capturing Value

Traditionally, when people think about the role of a product manager, people generally talk about working with a cross functional team (usually engineering, design, and data science) to deliver value.  I've come to believe that is necessary but not sufficient.

As a product manager, your day-to-day work is some combination of gathering information, synthesizing it, sharing it, and helping others make better decisions collectively.  When this work is only about delivering value to the user, the PM has not done a complete job.  Many times, the right problem to solve or the correct thing to build is different based on the organization's ability to capture the value that's created.

This is why PMs need to pay so much attention to pricing and packaging when thinking about prioritization.  If your current go-to-market strategy or your current pricing structure won't allow you to capture the additional value the proposed project would create, it's absolutely not worth prioritizing that project until you fix your GTM and/or pricing strategy first. 

For consumer/prosumer/SMB products, the value you're creating is often on one axis - access to songs for Spotify, access to the people you care about for social networks, storage space for Dropbox, and "store of information" for Slack, to name a few(1).  In the enterprise, there are often many different axes of value, some of which may pose tradeoffs to either the user or to the customer.  In these cases, having the value capture conversation before building anything is even more acute.

One last note: being clear about the ability to capture value can help avoid the next feature fallacy that can plague organizations of all sizes, not just those that haven't hit product-market balance(2) yet.  If the next feature doesn't give you any additional pricing/stickiness power, then it's not worth doing.

(1) This is why these organizations fight and fight and fight to introduce a second successful product, or to produce new user experiences that extend the core value.  For consumer, Facebook groups is a great example.  For prosumer/SMB, Dropbox's introduction of Carousel and acquisition of Mailbox are prime examples.

(2) One of my favorite quick posts; still holds up great even ten years later!

Product Tools and How To Use Them

There's a lot of advice around standard metrics: don't have more than 2-3% monthly churn, convert at least 2% of your free users to paid under a premium model, response rates should be 200 milliseconds or less, and so on and so forth.  There's a little less out there of *how* to get and measure these core metrics.  I wanted to share exactly what we track and how for Nylas Mail, the freemium cross-platform desktop email client I've been working on for the last few months.

We track four main things: user actions, performance, errors, and user happiness.  For each one of these core areas, we use a different tool.

User Actions: Mixpanel

For core user actions, we use Mixpanel.  Since Nylas Mail is an Electron app, it's just as easy for engineers to add Mixpanel events to Nylas Mail as it is to your standard web-based SaaS app.  We want to see what actions users are doing in Nylas Mail so we know what we're good at and where to improve.  Of course, we don't look at what people are sending or who they're corresponding with - that's not useful to us, it'd be a ton of data, and it's just plain wrong.  As it was the big feature when they launched, and still their best feature, we use Mixpanel funnels to track newly acquired users and try to make sure that we're eliminating all the rough spots so that we can get someone from trial to habit as soon as we can.  We also use Mixpanel's built-in notifications feature to do a drip of onboarding emails after a new user signs up.  I have lots of gripes about Mixpanel, which makes sense since it's a ten year old tool and things have changed in internet land, but it's still the best tool I know for seeing just what users are doing inside your app.

Performance: Honeycomb

Honeycomb is a relatively new entrant in the analytics space, and while it can be used for a lot of things, we use it to track performance.  In particular, we use Honeycomb to track 90th percentile performance versus counts on key events - this lets us make sure that we aren't introducing performance regressions as we push our new versions of the app.  There are great filters and ordering options, so we can slice and dice data pretty easily.  A really nice feature - Honeycomb runs are discrete events with discrete URLs, so we can paste these into Slack and refer back to that exact data set and those graphs days or weeks later.  (This sadly isn't possible in Mixpanel.)  Honeycomb is still new, so the ramp up period is a bit longer and you always have this feeling that you're not using the tool as well as you can, but once you find something that works, it's really addictive.

Errors: Sentry

We send errors to Sentry automatically.  We use this for two things: we want to see which errors happen the most often so we can prioritize bugs and we can also use Sentry to let us know if we've introduced new errors when we've released a new version of Nylas Mail.  We can see if a small handful of users are seeing lots of errors or if errors are being seen more broadly by a large set of users very quickly. We also look to see if errors are concentrated on a particular platform, release, or type of connected account (Google, Office 365, or IMAP.).   One thing to look out for: Sentry can get overloaded with errors very, very quickly if you ship something broken or are too generous with sending errors to Sentry, so beware of going over your limits.

User Happiness: Zendesk

Yes, Zendesk.  Lookit, for product managers or anyone building something where the customer is the user: vox emptor, vox dei.  The voice of the customer is the voice of God.  You can look at cohort data, you can ask for CSTAT and NPS, and you can dive into logs until the cows come home.  The best way to hear what the customer is experiencing is to hear it with their own voice.  When customers choose to reach out to you, it's your job to listen to every word they say.  If the customer says "the app is slow" but your telemetry shows that your response rates are under 200 ms, guess what?  Your app feels slow and it's your job to fix it, period.  We look at every support ticket as an opportunity to understand the problem that the customer has and for us to learn how they tried to use our app to solve it.  It's customer development, right in your inbox.  Zendesk can be slow and the analytics leave something to be desired, but it's a critical part of our product development process.

We've found lots of neat things with our data sources.  Some highlights: it turns out that sending emails is the very best predictor for retention, even though people receive a lot more email than they send.  Perceived performance is way different than the performance of the app - in both ways.  Electron may be cross-platform, but there's something about Windows users or Windows itself that throws a disproportionate number of pull-your-hair-out bugs.  And even the most non-technical users will jump through hoops to get you logs if you're patient and understanding with them.

Introducing Braid

Introducing Braid

One of the hard things about doing a startup is finding problem/founder fit. Since successful startups take forever, it’s really important for founders to go after a problem that they want to keep solving. If you’re going to end up working on something for a decade or more, you better know the problem really well and be highly motivated to solve it.

Some people are lucky — they have lots and lots of ideas for lots and lots of problems that they want to solve. They keep notebooks in their bags, by their bedsides, and in their glove compartments so they can write down ideas any time inspiration strikes. (Or, at least they did before iPhones.)

Anyway, I’m not so lucky. I’ve only had one idea I’ve been excited about for the last half-decade.

As I moved up in my career and moved from company to company, I found that I spent more of my time doing administrative work and less of my time doing the job I was hired to do. Building and problem solving gave way to tracking things down and filling out forms. I stopped being excited about my work and started dreading the artificial deadlines and TPS reports required to keep our teams in some semblance of cohesion.

For better or for worse, we define ourselves by the jobs we have. But when we go to work and we can’t even do the jobs we’ve been hired to do, it’s just a total waste. Handcuffed by tools chosen by IT and policies imposed to solve a problem one person had 15 years ago, we become exhausted and disillusioned with our jobs.

For me, at my recent jobs before starting this company, I became disillusioned and exhausted by the constant barrage of unnecessary fire drills and meetings that piled up on the calendar. Instead of being able to talk to customers and mock up wireframes, I spent most of my day making PowerPoints and writing long updates that no one ever read. People were less concerned about helping projects move along and more concerned about making sure they could blame someone else for the inevitable delay. It’s what I call the “cold comfort of soft numbers”.

No one is excited to come home and say “I went to four status update meetings today!”. No amount of money or private offices can replace the joy that comes from doing a job well. What we want as employees at an organization is pride of ownership — to be proud of the thing we built, the team presentation we delivered that impressed the client, or the finally solving that problem bedeviling the team for the past three weeks.

I wanted to build a tool that just let me — and my friends — get back to work and work better together.

Braid is designed to let teams work better together—by taking advantage of the work that we’re already doing. We’ve added Braid to be a light layer on top of Gmail and Google Calendar, targeting those organizations that live in their inboxes.

Braid is a collection of simple news feed feeds that are available where you need them — in your Inbox, and out of your way when you don’t. It’s simple to add emails to a feed with a click of a button — no more copy and pasting from an email into a wiki or a task list. Add events or jot a quick note as well. Upload files so that they’re all in one place. Tying together all the important things we do in one cohesive place is what we’re about.

The motivation behind Braid is to build a tool that respects people and respects their existing workflows. We believe that Braid will help you get better results for your projects. Braid is a quiet enabler instead of a chore. Braid is a tool that enables people to get credit for what they’ve done when they’ve done it. And the bonus is that managers and clients can feel secure seeing the progress of a project in real time.

Braid is built to be a single, simple source of truth that everyone can actually trust. So there’s more time to get things done and everyone is pulling together.

I hope you’ll try Braid and see if it helps you and your team free up more time for the things that truly matter. If you want to read more about Braid the product, check out the launch post. And please reach out with your ideas to make it even better. Thanks for reading.

Please Shut Up About Growth Hacking.

(This post originally appeared on my Svbtle site:


Point one: growth hacking isn’t new.



Point two: growth hacking doesn’t work if your product sucks.







PCI Compliance In The Cloud: This Changes Everything

Amazon announced today that they have PCI compliance certification for the entire AWS stack: EC2, S3, EBS, and VPC.  This is huge.  Almost every startup these days uses some cloud hosting provider, and until now, it's been literally impossible to be PCI compliant in the cloud.

To be PCI compliant, the website owner needs to be able to provide physical access to the servers in the event of a credit card breach.  If you're running in the cloud, you can't provide physical access to an auditor, since you have no way of gaining physical access yourself.

The merchant account providers don't know the first thing about hosting, and they don't really care.  And no startup I know has moved to bare metal and hired a sysadmin just to follow the letter of the standard.  Startups have better things to do than subject themselves to an audit by Trustwave or some other QSA that certifies PCI compliance.  (See, you thought you were PCI compliant, but you're not.)  But if some companies now magically have PCI compliant clouds, then they have every incentive to rat on their competitors who aren't to Visa/Mastercard, effectively shutting down their ability to process credit cards.

Given that this is a rather large deal, I've asked Amazon PR to send me a copy of the QSA report.  Just to prove to yourself that this is a big deal, look at the list of PCI compliant providers: (PDF link)  Amazon is like that Sesame Street song: one of these things is not like the others.

One of things I want to figure out is if Engine Yard's EC2 instances are de facto included in the PCI compliance report, or if only customers contracting directly with Amazon are covered.  Hopefully, the QSA report answers this, but if not, I'll try to run this down with Amazon and Engine Yard.

Upshot: my best guess is that this raises the table stakes for every other cloud provider out there, and if you're in a competitive market and you're not on AWS, your competitors can attempt to report you for PCI violations.  You should ask your cloud provider when they'll provide PCI compliance, and if they can't give you a roadmap, you should investigate moving to Amazon.  


Blueleaf is building the world’s first truly personal financial planning platform.  It’s a complex product with a lot of features to meet all the different problems that our customer discovery has shown that people want.  Here are ten concrete things we’re doing to get 10,000 sign ups before we even launch our product.

1. Making Potential Users Ask Publicly To Get In

There are two ways to get into Blueleaf: get an invite from us, or get an invite from a current user.  We let in a limited number of users every week, and we choose who we let in based on how much they want in.  Only people who request an invite and follow us on Twitter, Like us on Facebook, or otherwise make it clear that they want in, get in.  This means they have to sign up with us and tell everyone else about us before they can get in.

2. The World’s Strictest Invite System

The other way to get in is to get referred in by a current user.  We’ve developed our own twist on refer-a-friend: rather than limit the number of invites someone has, there are an unlimited number of invites – but we’ve limited the time frames to invite a friend.  We turn on the ability to invite a friend for just an hour or two so that people who want in have to beg everyone they know who’s on to let them in before the window closes.  When we announce that invites are on, potential users need to plead for invites publicly on Twitter and Facebook, privately over IM and e-mail, or however else they can reach current users.  Again, this kicks off a viral loop before the app has even launched.

3. Splitting Up Blog And Library Content

We write – a lot.  We publish something new almost every day.  However, most of our new content isn’t on our blog – it’s in Blueleaf's library of articles about financial planning.  It makes no sense to hide an article about bond funds and bond ETFs on a blog, where it’ll be impossible to find in a month.  We’ve segregated our greenfield content so that someone looking for that topic five years after we publish it can find it easily.  Plus, we can easily update and change this content as laws, tax policy, and the investment environment changes without confusing new or returning visitors. 

4. Having A Strong Point Of View

When we write content, we rarely do six of one, half a dozen of the other.  When we write about Roth versus Traditional IRAs, we don’t do pros and cons.  We say that if you have to ask the question, you should open a Roth IRA.  The vast majority of Americans qualify for a Roth.  They should open a Roth.  For the people who should open a Traditional IRA, we go through the reasons when it would make sense – but we don’t do false equivalence.  On our opinionated articles, Blueleaf’s position is front and center, up front, before the rest of the content to deliver as much value as we can in as few seconds as possible. (BTW, we do absolutely no SEO analysis or keyword stuffing.  That stuff is lame.  We write answers to the questions people ask us, simple as that.)

5. We Don’t Blog About Our Product

The Blueleaf blog has three components: Blueleaf Stories, Blueleaf Thoughts, and (to come) Blueleaf Tech.  Our Stories are the Blueleaf staff writing about their own personal financial experiences so that we can make it clear that we’re making a product that we’re very emotionally invested in.  Over time, we’ll ask our users to contribute their own.  Blueleaf Thoughts are about things we find interesting that we think will also be interesting to our audience.  We want to provide value for everyone who is saving for their financial futures, regardless if they’re interested in our product right now or not.  If we have interesting stuff, we’ll get links and traffic.  That’s it.

6. Link Roundups For Users And Relationships

The other thing we do on our blog is post twenty links every Friday afternoon, comprised of the four handpicked links we tweet out each weekday.  Not everyone follows @blueleafcom on Twitter, so it’s a nice convenient place to have some leisurely reading over the weekend.  However, the real clever thing about link roundups is that they provide Trackbacks to the financial bloggers we want to establish relationships with.  Bloggers click through on their Trackbacks, see the Blueleaf site, and get interested in the product.  This makes it much easier to develop relationships and approach them for coverage as we get closer to launch.

7. Using Facebook And Twitter Very Differently

Instead of using our blog to announce new features, we use Facebook Notes.  Also, Facebook is the only place to get a feed of every new piece of content we post when we post it (there’s no RSS feed for our Article content).  Facebook is Blueleaf's broadcast medium for people who want to keep up-to-the-minute with what Blueleaf is up to.  We use Twitter to share interesting links and we’ll use it as a cornerstone of our customer service as we add additional users.  We’re so big on sharing links on Twitter that we have two accounts for it – @blueleafcom and @BlueleafLinks.  The only thing we do on both?  We’re diligent about responding to anyone who comments on Facebook or @replies to us on Twitter.  

8. A/B Testing The Hell Out Of Everything

We A/B test a lot – we’ve tested calls to action, button colors, button size, headlines, images, and a litany of other things using Visual Website Optimizer and Performable.  But we make sure we don’t end up in local maxima.  We’ve A/B tested radical redesigns of our homepage, and the current page is the one that beat the pants off our old one.  We do this A/B testing so that we can maximize our conversion, regardless if the traffic to our site is a trickle or a flood.  We’re ready to catch all the fish in the sea that just happen to be swimming by.

9. Being Smart About Paid User Acquisition

We’ve tested all sorts of various paid acquisition channels – everything from Google and Yahoo to reddit, Facebook, and directory sites.   We’ve been able to drive down our Customer Acquisition Cost (CAC) to a very reasonable amount – not the blended CAC between paid and free, but our CAC on paid alone is very, very attractive.  Even though I’m the guy who called AdWords “a gateway drug to unprofitable user acquisition”, being smart with small paid tests that get your CAC down to a reasonable number makes potential investors all hot and bothered.  Proof that you can get affordable paid acquisition makes fundraising much, much easier.

10. Knowing Just Who The Hell Is Signing Up

We run every single e-mail we get through Flowtown so we know a bit about who’s coming in through the open door.  Doing this, we can stagger who we let in when and we can have better content for our e-mail newsletters to those on the waiting list.  We reach out to people we’ve identified as potential influencers and we make sure that we don’t let people who are potential investors until the time is right.  (Join the club, folks – not even our current investors have access to Blueleaf.)  Letting in the right people at the right time means that we prime the pump to yield water only when we’re thirsty for new sign ups.

Be Careful About Outsourcing Your Customer Acquisition

One of the great things about services like AdWords, Wufoo, Mailchimp, Flowtown, Performable, and so on is that they allow the marketing side of a startup to work independently of the engineering side of the startup.  Whip out your credit card and you can have a source of traffic, lead generation forms, e-mail marketing campaigns, social media insights, A/B testing of your landing page, and all that great stuff.

The problem with this is that as these tools have begun to play better together (thanks to the magic of Webhooks), your data becomes a bit more trapped inside each of these programs.  It can be hard to audit your data and even harder to integrate this data into your core application.  You end up going to each service independently to answer basic questions such as "when did this user give us their e-mail address?" and "just where did we get this e-mail address from?"  And if you want to answer more complex queries such as "just what is our overall (blended) customer acquisition cost (CAC)?", you have to export your data into CSVs and manually massage them together, which can be a very painful process indeed.

The bigger issue is when you try to integrate this information with your main app so you can do cohort analysis.  Cohort analysis is the magic analysis that tells you how you're doing on your key retention and engagement metrics over time: "did our June signups come back to the site more often than our April signups did?"  Trying to import user acquisition dates into your database of existing users (once you've sent them an invite to your app) is very time-consuming as you want to make sure that you don't break anything - there are a large number of edge cases you have to deal with: you'll have users who gave you their address more than once (for example), you'll have users that have changed their e-mail address inside the app from the one they gave you on your lead gen form, and you'll have users that have invited other users.

When you're a pre-launch or early startup, you don't have a lot of data points to deal with.  This is good because it means that you can, with effort, use Excel or some other tool to tie together all these different repositories of data.  But it's also bad because you may not think to have systems in place to more elegantly handle measuring your AARRR metrics post-launch.  You'll be so busy putting out fires and doing PR that you may end up neglecting instrumentation.  

While you may not have to do everything in-house, it's critical to have an engineer on your team who's involved in business/marketing support from time to time.  Defining and implementing an integration and migration paths (a lot of these services *do* have APIs for example, but those aren't something the mouthbreathing "business guys" can do anything with) before you launch is critical to make sure that you can calculate and measure the things you'll need to calculate and measure as you scale your business.


Lapsed Users - Your Most Valuable Untapped Resource

You're struggling with user acquisition.  No one's coming back.  Your product is robust and full-featured and you're adding new features every week.  You're only building the features that your users want, so you're not wasting any time on "wouldn't it be cool if" problems.  But no matter how hard you work, your graphs just aren't up and to the right. 

What to do?

One of the most valuable resources that startups (consumer web, again) have are the e-mail addresses of their registered but lapsed users.  It can be very valuable to reach out to them and figure out what part of your message or product didn't resonate.  Remember, if your "very disappointed" score is between 25% and 40%, it's often the message - and not the product - that isn't resonating.

Of course, if only 2 or 5% of your registered users remain engaged, it's probably both the product and the message. 

Here's a simple way to find out what's going on.  First, find a well-defined cohort of users.  This cohort could be from your last marketing push, or even "all users who signed up in winter" - you want they survey respondents to be as similar to each other as possible.  Grab the e-mail addresses for all of the ones who registered who fall out of your engaged metric (last 7 days, last 30 days, etc).  Send those lapsed users from that cohort the following e-mail:

Dear $user,

Thanks so much for signing up for $product!  We noticed that you haven't been back in a while, and we would love to know what we could do to make $product better for you.  If you click on the link below, we have a quick, two-minute, four-question survey that would really help us out:


If you fill out this survey, you'll get $free_product/be entered to win $free_product/have our undying gratitude.

Thanks so much!

$founder_1 and $founder_2

That's it.

The survey should have these four questions:
  • Why did you sign up for $product?
  • What did you think you were getting with $product?
  • How did $product disappoint you?
  • What can we do to make $product better for you?

These are, of course, unstructured questions, so you're going to have to read all the answers.  Don't worry about missing stuff - the patterns will be repeated over and over again so you won't be able to forget about them.

If you want, you can add a checkmark box or a field to capture phone number for follow ups.  Make sure that you don't ask for name or force respondents to leave any personal information if they don't want to.  You want them to give their unvarnished feedback.

Take their feedback - figure out if it's the product or the messaging that's falling short.  If it's the product, add those features (and think about killing the ones they're not using).  If it's messaging, that's even easier to fix.


















As far as I'm concerned, there are three real options:
  • PayPal Website Payments Pro
  • Braintree Gateway + Account

