Draw on napkins. Better yet, take me out for beers and we'll both draw on napkins.
As several of you know, my job is to manage a handful of SaaS (software as a service) apps. I've also had conversations with several of you that were asking about what exactly that entails, so here's a glimpse (spoiler alert, there are lots of acronyms).
Learn fancy acronyms at blazing speeds! Impress your friends and coworkers with this handy guide.
Har har title puns. This is written about running digital products (like Curated, the newsletter service I use to send you these links), but I think it could be tweaked slightly to help you with any internal projects you do at work. The takeaway is that your team should work on projects that make your product/service more valuable to your customers. That means don't build things because you have hunches that it will make your product/service more valuable. Data > hunches.
I've read a tiny little bit on the Jobs To Be Done framework, so I can't comment much on that yet. But I think the proposed statement to align your team is really good, and I feel this guy on the "late adopter of Snapchat" situation. Honestly, still not entirely sure how that app works. But I open it sometimes.
"Alexa, buy me some Bitcoins."
Definitely light, easy-listening kind of stuff here.
I use Intercom every day for customer support and customer data, so I'm a big fan. They make my life so much easier. I read their updates because they have a really fun voice and tone: it's like they don't necessarily know how all of this is going to work out but they're excited about it.