Interesting. Can you describe what your (previous) team worked on? Was it an engineering team? I have experienced many good engineering teams who discuss calmly and with little friction, but when the big business stakeholders (and egos) come in, it's a different story.
It was an engineering team but we had a mix on the room of engineering, PMs, and senior leadership.
It was a very stressful project, we only had a tiny % of the resources we needed, and everyone had their belief as to the best way to navigate the maelstrom and come out the other side.
We were also all very invested in the product space (fitness) but in different aspects of it (e.g. running vs weight training) and we had no budget for market research. So for a long time (until BJ Fogg came along!) feature planning was "who is arguing the loudest for their point of view".
Then again this was classic Microsoft for the longest time, after all this is the company that had weekly "war room" meetings.
Re:Fogg Behavior Model
by captain_crabs on Saturday February 22, 2020 @01:13PM
(#22392380)
How's the process of getting him to present go? I'm interested in doing the same!
I actually have no idea, but I know he does it regularly! He discussed doing it at other companies so I know we weren't a one off!
The lesson on feature planning was revolutionary for my team. We went from shouting and arguing during planning meetings to everyone walking out happy with all the decisions that were made. He teaches a truly amazing process.
The behavior model itself is super useful for user journeys. My biggest take away is that when someone first downloads an application (or signs up on a website) they do so because they have a problem they want to solve, and at that moment there is a level of motivational energy that they are willing to spend. Be it adding pictures to a dating app or going through an onboarding process. If that first use is too complex, the user's motivation is exhausted and they'll drop out.