Last night, we at @linear hosted a design leadership event. We invited about ~25 design leaders from top companies to join @lil_dill and me to discuss b2b design, quality, and craft.
There were many good comments and questions that came out of this. I'll try to see if I can share them somehow, but first, I wanted to share why I was interested to do this event:
I often hear design talked about generally or in the abstract, but I haven’t really seen people highlight how design and practices differ between b2b vs b2c design.
Traditionally, design hasn’t been prioritized in the enterprise, but I believe design can be much more important there than on the consumer side.
Enterprise or professional software often provides tools or solutions to someone to create or generally do their job or do it better. The bar for the solution can be very high, and the user is very discerning of that solution. If the design tool the designer uses isn’t that good, the quality isn’t there, and it’s very apparent.
Since people are relying on the service to do their job or run their business, the stakes and need for reliability are also higher. If you constantly A/B test random things, it can cause disruption to the workflow, and therefore in the operations of the company. Design choices and changes should be considered and validated with beta programs.
Almost all companies serving other companies are in retention and usually also in net retention business. Ideally, you keep your customer forever, and you want the account to grow over time so their net dollar retention goes over 100% year after year. Design can have a huge impact on building loyalty. One main reason companies churn from products is when the product quality and design speed drop. Customers get frustrated, so they start looking for other options. Good design has the power to do the opposite. If you consistently delight the customer, you build up that loyalty and trust.
I think landing customers can be a finicky process. There might be many people in the process trying to evaluate your product against some other product. Usually, customers cannot inspect your code, or even fully grasp the product strategy, but one thing they can do is experience the product experience. Good design (and obviously the quality of the product execution) can really elevate that experience and be the thing that gets the customer excited about your tool.
But it's not all roses. The reason why design is hasn't been traditionally prioritized in the enterprise is that enterprise software has buyers and users. The buyers often don't use the product or even try it. If you work in a company that gives you janky tools, it's probably because the buyers had other goals and the product experience inconsequential to those goals.
But I don't this is practice is going to sustain.
The pressure and demand for well working and well designed enterprise tools will continue to rise and eventually buyers will realize why they are there – to elevate their teams with the best tools available.
This actually happened to Evernote. They took the advice of “keep talking to your customers and ship whatever they want” as the only guiding principle for product development. And what ended up happening was paying users liked it, but the product become unintuitive and feature overload for the new user. To the extent that they had to rebuild a version for the new user.
Users don’t always know if they really want something. It’s your job to take the extra step to think on their behalf: whether they really need this. Or can what they ask be done through something much simpler. Or can you solve multiple problems of different users with one new redesign rather than a bunch of changes. The right principle is: “Keep talking and listening to your users, spend the additional time thinking on their behalf what they actually want, and ship that”.
@maximesimeon Hi @maximesimeon Vanmoof seems dead in next months ... https://t.co/TlSpAgSlg7 if it not allready the case.
A friend in bike tells me these brands make beautifull bikes but very hard to repair... fyi
This is one of my favourite examples of a workflow.
"How Slack decides to send a notification."
Keep this in mind the next time someone asks you to design a "simple" feature.
@maximesimeon In pure css there will be masonry grid, currently not compatible in all browser is an early feature. You have a bunch of js libs for this ex https://t.co/DGl5eybevJ