A while back, I did a blog on how to get people to retain information better, replacing ‘boot camps in Bali’ with more thought-out mentorship-based approaches. That’s all well and good for internal training or even high-touch customer training on complex systems, but what about more simple products? Systems designed with Ease of Use as a core tenant? Can we ignore this involved method? Are boot camps back? (spoiler they are not) how do we enable customers at scale in velocity product motions?

Well, I am glad you asked!

Enablement does not need to be heavy-handed; it should fit the situation.

So what do you bring to the table?

Nov 3

Written By Jeffrey Matthews

This interview question has been at the forefront of my mind for the last week or two, and I wanted to address it from a few angles. First, I will answer it: good practice on my end (not to mention advertising, looking for work over here!) and a good example, and then I will dissect it and what it gets at in the interview process. While it may be asked in different ways, this was one of the more direct versions I have encountered, and it's worth consideration.

As a followup to my piece on how to be laid off I felt it would be irresponsible to ignore the other (happier) half. Getting hired is, usually, the goal of being unemployed so completing the cycle in article form seemed the for the best.

A mentor of mine once used this phrase and I have never gotten enough of it. This concept and its usefulness is what we will explore today.

This article will review the traditional enablement patterns and what our current technologies can do to get more bang for our learning buck.

Well, the easy answer is be in a redundant position, hey that’s even what the British call it!

But seriously this is about what to do after you get laid off and how to do it correctly. As I work through my second time being laid off, I am finding the systems that I (and credit where its due, my wife) developed to cope with the mental and physical realities of getting laid off have continued to have value.

A reflection on the tech industry evolution from 2012-2022 with respect to remote work.

An introduction to the the point of the blog.