Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
**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
Unfortunately, it’s not as simple as talking to customers every week. That’s a good start. But we also need to consider the rest of our continuous-discovery definition: At a minimum, weekly touchpoints with customers By the team building the product Where they conduct small research activities In pursuit of a desired outcome I’ve met many teams who are good at talking to customers. But they forget that the purpose of these customer touchpoints is to conduct research in pursuit of a desired outcome. Those last two lines of the definition are critical. We aren’t doing research for research’s sake. We are doing research so that we can serve our customers in a way that creates value for our business.
Continuous Discovery Habits
Teresa Torres
Next, agree upon metrics of success. Eric Ries is great at this, so read his books The Lean Startup and The Startup Way to learn his in-depth methods for what he calls “Innovation Accounting.” But in short, the small team needs a set of metrics to define what a successful experimental outcome looks like. Note, these aren’t long-term business metrics; these are short-term experimental outcomes. Eric calls it validating your blind-faith assumptions.
Ask Your Developer
Jeff Lawson
...catch up on these, and many more highlights
Readwise