Once you see that an answer is not serving its question properly anymore, it should be tossed away. It's just their natural life cycle.
They usually kick and scream, raising one hell of a ruckus when we ask them to leave. Especially when they have been with us for a long time.
You see, too many actions have been based on those answers. Too much work and energy invested on them. They feel so important, so full of themselves. They will answer to no one. Not even to their initial question!
The hardest thing about customer interviews is knowing where to dig. An effective interview is more like a friendly interrogation. We don’t want to learn what customers think about the product, or what they like or dislike — we want to know what happened and how they chose... To get those answers we can’t just ask surface questions, we have to keep digging back behind the answers to find out what really happened.
I hadn't realized that Medium had made JavaScript a requirement to be able to read any Medium post - I'd had JS disabled for ages on Medium just because of all the extra cruft they added.
But now, without JS, you only get the first few lines of content, and the rest is loaded entirely with JS - which is...stupid.
Scribe fixes all that and focuses entirely on the author's content.
Why Would I Want to Use This?
You believe in an open web
You believe more in the author than the platform
You don't like the reading experience that Medium provides
You object to Medium's extortionist business tactics