4 ms·
Anti-Personas
- neom 3y agoArch users.
- cheschire 3y agoHow do we use or reference them? Should we have anti-epics and anti-user stories? Do we validate the anti-behaviors with rejection criteria?
- codeduck 3y agowhat about user anti-stories? where do those fit in?
- antifa 3y agoTo me, "User wants to do something we don't want them to do" sounds like it would be an safety/authorization/security/sales funnel story 99% of the time.
- mortenjorck 3y agoPerhaps you're being facetious, but this is actually kind of an interesting idea, at a high level. Probably not something to do in your regular sprint planning, but as a part of strategic discussions, maybe at an offsite, the idea of creating a few anti-epics to help build focus seems like it could have some value.
- cheschire 3y agoI was being facetious but only because I felt like the article felt like half a concept. I have some guesses about how it might work, and you've taken it another step further. But I was actually considering it as I wrote, thinking perhaps an anti-user story for a site like HN would be "As a sales person I want to astroturf interest in my company's product using puppet accounts so that I can generate sales." or "As a nation state I want to brigade topics that present my nation in a poor light." So yeah, facetious, but legitimately considering it too.
- gavmor 3y agoYes! We should have anti-user stories! The only question is; how to index them when writing stories so that they're queried at the right juncture to abandon? Generally, we accrue these anti-stories as a sort of oral tradition, the classic example of which is "we tried that before, it didn't work." Any [junior] dev worth her salt will, when arriving on a team, start to question all the Chesterton's Fences strewn about the place. That's when we start reciting the anti-epics! Why not codify it? Admittedly, from my perspective, Chesterton's Fences are technical in nature, but I imagine analogous interactions occur at the product level.
- cheschire 3y agoYep, there's plenty of business process level instances as well. They tend to be in the form of "pointless" meetings or other process steps that people feel are "bureaucratic gatekeeping". When creating line of business apps these chestertons fences can appear when a product owner does not fully understand the complexity they're supposed to be owning, and they remove / fail to capture critical validation steps in a process for the sake of efficiency.
- phailhaus 3y agoAnti-personas are used to give you grounds to reject work, not create it.
- M2Ys4U 3y agoNot necessarily. An anti-persona could highlight features that you need to introduce to prevent behaviour you don't want. As an example: An anti-persona could be "An abusive ex-partner who wants to harass another user of the program", and the new work to be created would be things like "adding the ability to block other users", or "adding visibility controls" etc.
- marcosdumay 3y agoAnti-scope has been in common use for decades already.
- m463 3y agoI can't help but think of anti-personas, like folks who value privacy, who dislike installing apps, folks who hate in-app purchases, or folks that dislike subscriptions. Leave these out and you have a money funnel with little or no friction. Apple pioneered this, and I remember the steve jobs presentation where he talked about all the users, each with a credit card on file (required).
- downWidOutaFite 3y agoThanks for this. One of the reasons I refused to use iPhone is that you HAD to have a credit card on file (have they relaxed this?). Now I can tell people that try to convince me to switch to iphone that steve jobs didn't want me as a user.
- rab1d 3y agoI’ve never had a credit card linked I just use a Venmo debit card with nothing on it and not attached to a bank account.
- hollerith 3y agoDoes the Venmo debit card know your real name?
- waboremo 3y agoThey have, you can now select "none" when creating an Apple ID for the billing information. I believe the only way previously to get around this issue for a while was to buy a new Apple device because the initial device setup allowed for an Apple ID creation without billing info demands.
- antifa 3y agoI found that I couldn't accept free appstore (on MacOS, not iPhone) offers without a credit card on file a few weeks ago.
- JohnFen 3y agoThis (generally, not the CC thing specifically) is the reason why I stopped dealing with Apple devices. Apple doesn't want me as a customer. That's not a bad thing, or a thing I feel any sort of resentment about. Apple just has a very specific demographic in mind, and I am not in that group.
- PlunderBunny 3y agoAn anti-persona I invoke in my mind is my mother - she loves her iPad for keeping in communication with my sister and me, but I have to keep turning off new features after updates to reduce the complexity and keep the interface simple for her.
- brody_hamer 3y agoI was thinking about this, too. Or how, often we write our personas by defining what they are, when we ought to also define what they are not. Ex: John is a c-level exec. He wants to feel like he has all the information at his fingertips, but he will not take the time to read any dialog, or apply any filter. They will just “export all”.
- cvccvroomvroom 3y agoWhat good was this article? There's no message, no explanation, no examples, and no context.
- aaron695 3y ago[dead]
- erhaetherth 3y agoYou have to buy the book ;) It also has no explanations, examples, or context.
- deleted 3y ago[deleted]
- jschveibinz 3y agoWithout seeing the author’s book, I would like to suggest a couple of potential ways to think about this given the short article: If the customer is the person your trying to sell to, then who is the anti-customer? A: The person you can’t seem to sell to. 1) Your persona says everything about the target customer relevant to your product. But which of these aspects of the customer persona make them hard to CLOSE? How does this analysis impact your marketing and sales approach? Your product? Your business? 2) Another option is to see the anti-persona as the “failure” to REACH your customer because of hidden aspects. Identify potential hidden aspects that can result in a failure to sell as your product, business or strategy is currently envisioned.
- ang_cire 3y agoI think the author is rather saying that anti-personas are people you DO NOT WANT to sell to, not ones you just have a hard time with. For instance, if I am a B2B product that really requires a large-scale (say, 10,000+ endpoints) deployment to really become valuable to a customer, I really should try to avoid selling to a 300-endpoint small business. And I sure as hell don't want to sell it to some random grandma who's not even running a business. I won't flat-out refuse, but it's not going to help me or them to give them a product that is mostly useless to them. It hurts them because it's a waste. It hurts me because now I'm either setting up a future disappointment, or I'm potentially going to expand my product scope/features to try to become useful to this new group. A product can't be everything to everyone, and just as it's important to understand what your product will do, and who it will be for, it's important to understand what you refuse to let it ever grow into doing, and who should not consume it as a result.
- JohnFen 3y agoYes, an excellent point. It's a variant of a business rule of thumb that I learned when I was younger that has served me well over the decades. "No" is the most valuable word you have. Use it. It's easier to go broke by saying "yes" to the wrong thing than by saying "no" to the wrong thing.