Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
However, if it's the first time they have worked on this problem, then they will likely need some time to learn the space, start collecting some data to establish a baseline, and get a sense of what the possibilities are. In this case, encourage the team to jump in and not get stuck in paralysis by analysis, and acknowledge with them that they will learn much more as they progress, and that the confidence level will, of course, be low in this first quarter because they are still learning what they don't know.
Empowered
Marty Cagan and Chris Jones
**Your Action Steps**
It’s time to put these takeaways to the test.
1. **Choose your most common task**
Pick one writing task you do repeatedly (like team updates, client emails, or meeting summaries). This will be your testing ground for the results.
2. **Create your AI advantage**
Simply type: "You are a senior [your role] with 15+ years of experience. Help me create [specific task] that is [clear/professional/engaging]. Here's what I have so far: [your content]". Then follow up with additional direction or clarification.
3. **Measure your success**
At the end of the task, track the same metrics from the study to understand if you saved more than 37% of your time, completed higher quality work, and enjoyed the process.
🤯 Day 2: How to Be 37% More Productive at Work
AI University @ The Rundown
The top-down, change-resistant planning we see in the Fire Phone story is all too common. It’s the norm in large organizations. Most often it’s expressed in a document called a feature road map. This is a compelling document. It gives a clear sense of where we are, where we’re headed, and what features we’ll build to get from here to there.
Sense and Respond
Jeff Gothelf, Josh Seiden
...catch up on these, and many more highlights
Readwise