Systematic theoretical analysis of the methods applied to a field of study
POPULARITY
Categories
149 episodes with Methodology
88 episodes with Methodology
89 episodes with Methodology
56 episodes with Methodology
29 episodes with Methodology
38 episodes with Methodology
37 episodes with Methodology
34 episodes with Methodology
30 episodes with Methodology
75 episodes with Methodology
16 episodes with Methodology
28 episodes with Methodology
23 episodes with Methodology
22 episodes with Methodology
10 episodes with Methodology
14 episodes with Methodology
7 episodes with Methodology
33 episodes with Methodology
12 episodes with Methodology
8 episodes with Methodology
15 episodes with Methodology
21 episodes with Methodology
11 episodes with Methodology
11 episodes with Methodology
11 episodes with Methodology
17 episodes with Methodology
15 episodes with Methodology
12 episodes with Methodology
11 episodes with Methodology
8 episodes with Methodology
8 episodes with Methodology
7 episodes with Methodology
15 episodes with Methodology
9 episodes with Methodology
5 episodes with Methodology
12 episodes with Methodology
11 episodes with Methodology
5 episodes with Methodology
14 episodes with Methodology
20 episodes with Methodology
8 episodes with Methodology
9 episodes with Methodology
8 episodes with Methodology
6 episodes with Methodology
8 episodes with Methodology
6 episodes with Methodology
10 episodes with Methodology
13 episodes with Methodology
5 episodes with Methodology
7 episodes with Methodology
28 episodes with Methodology
4 episodes with Methodology
7 episodes with Methodology
6 episodes with Methodology
16 episodes with Methodology
6 episodes with Methodology
6 episodes with Methodology
6 episodes with Methodology
10 episodes with Methodology
5 episodes with Methodology
8 episodes with Methodology
7 episodes with Methodology
6 episodes with Methodology
15 episodes with Methodology
8 episodes with Methodology
4 episodes with Methodology
9 episodes with Methodology
4 episodes with Methodology
11 episodes with Methodology
3 episodes with Methodology
5 episodes with Methodology
5 episodes with Methodology
5 episodes with Methodology
5 episodes with Methodology
5 episodes with Methodology
6 episodes with Methodology
7 episodes with Methodology
6 episodes with Methodology
6 episodes with Methodology
6 episodes with Methodology
6 episodes with Methodology
3 episodes with Methodology
5 episodes with Methodology
5 episodes with Methodology
13 episodes with Methodology
5 episodes with Methodology
3 episodes with Methodology
4 episodes with Methodology
6 episodes with Methodology
8 episodes with Methodology
7 episodes with Methodology
3 episodes with Methodology
4 episodes with Methodology
5 episodes with Methodology
6 episodes with Methodology
4 episodes with Methodology
4 episodes with Methodology
2 episodes with Methodology
5 episodes with Methodology
3 episodes with Methodology
3 episodes with Methodology
7 episodes with Methodology
3 episodes with Methodology
3 episodes with Methodology
3 episodes with Methodology
6 episodes with Methodology
4 episodes with Methodology
2 episodes with Methodology
3 episodes with Methodology
7 episodes with Methodology
4 episodes with Methodology
2 episodes with Methodology
2 episodes with Methodology
3 episodes with Methodology
3 episodes with Methodology
2 episodes with Methodology
4 episodes with Methodology
3 episodes with Methodology
2 episodes with Methodology
2 episodes with Methodology
2 episodes with Methodology
2 episodes with Methodology
12 episodes with Methodology
11 episodes with Methodology
2 episodes with Methodology
3 episodes with Methodology
Jason catches up with ATLUTD Director of Methodology Javier Perez looking at the recent successes and growth in the Academy- starting with MLS Next Cup in UtahThey also look at the responsibility attached to representing the values of Atlanta United from a young age and how the club continues to evolve- even as successes continue to come for the franchise
Platform vendors are transferring liability and delivery responsibility for AI services onto MSPs by building structured AI practice frameworks, training programs, and service delivery methodologies. This approach is motivated by mounting economic pressures on vendors, as seen with large-scale infrastructure investments and the need for sustainable revenue models. PAX8, Ingram Micro Cloud, ConnectWise, and others are formalizing AI partner programs that enroll MSPs to deliver vendor-defined services, while shifting operational complexity and accountability downstream. The episode highlights PAX8's Managed Intelligence initiative, aimed at helping small and midsize MSPs deliver AI services to SMB clients with minimal prior expertise. PAX8 cites its own research, which notes that 62% of SMBs view AI as essential for competitiveness and 74% plan to increase AI spending in the coming year. The economics of AI scaling are underscored by data on projected data center buildout costs—up to $15 trillion by 2030 and requiring $1.75 trillion annually just to maintain. OpenAI's public offering, with an $850 billion valuation and $180 billion in funding, is attributed to the need for capital that private markets can no longer supply, prompting vendors to leverage channel partners for both revenue generation and market validation. Supporting developments include expanded programs at the distribution and platform levels: a PAX8-Nocdoc partnership providing managed NOC/SOC services for smaller MSPs, Ingram Micro Cloud's collaboration with PartnerStack to formalize AI service delivery infrastructure, and ConnectWise's introduction of an AI-native platform for predictive and autonomous IT operations. Research from Omnia and the IBM Institute for Business Value indicates underutilization of vendor market development funds and widespread deployment of AI frameworks despite only 11% of tech leaders feeling prepared—demonstrating the gap between vendor offerings and operational readiness. The implications for MSPs are significant. By enrolling in these vendor-driven AI programs, providers take on delivery risk, contractual accountability, and potential liability for AI outcomes they did not design. The structural split is clear: MSPs can either create and govern their own AI methodologies—pricing accountability as a service—or become vehicles for vendor frameworks, absorbing complexity without full compensation or control. Practical recommendations include updating service agreements for AI-related risks, building internal governance around AI deployments, and not allowing vendor or community consensus to substitute for explicit accountability for outcomes. 00:00 Channel AI Shift 03:59 Enrollment, Not Enablement 06:55 Methodology vs. Liability 10:01 Why Do We Care? Supported by: Zero Networks CometBackup
Key account management is more than a sales tactic — it is an organization-wide growth strategy that prioritizes deeper, value-driven relationships with your most important customers. On this episode of the podcast, Joel Schaafsma joins me to dig into the nuances that differentiate key accounts from regular accounts, why organizations struggle with defining them, and the organizational investment and ROI linked to strategic account management. Joel is a strategic account management and customer experience expert known for driving organizational growth and building frameworks that translate customer insights into better business decisions. He shares his experience on evolving from vendor relationships to trusted advisor status, the common mistakes made when transitioning from sales to account management, and the critical importance of aligning your business strategy with your customers' objectives. Outline of This Episode [00:00] Key account strategy overview [05:34] Building customer alignment [07:43] Stakeholder mapping for alignment [11:17] Key account management basics [13:37] Collaborating on customer-focused strategies [16:34] Key strategies and common pitfalls [21:31] Building a hospital partnership program Building a Key Account Strategy That Aligns With Customer Goals You build a winning key account strategy by aligning your business completely with your customers', integrating at multiple organizational levels. By orchestrating input from all stakeholders, not just the primary point of contact, account managers can spot trends, proactively address issues, and introduce co-creation opportunities that serve both parties' goals. Leveraging Stakeholder Mapping and Executive Sponsorship Deep alignment is only possible with clear stakeholder mapping. This goes beyond knowing names on an org chart, it's about understanding influence, needs, and potential advocates across both organizations, which equips you to withstand changes such as leadership turnover and evolving expectations. Joel emphasizes the role of an executive sponsor program: connecting your senior leaders with theirs builds credibility, opens doors for value-driven dialogue, and quickly removes barriers when action is needed. Tools, Technology, and Methodologies for Success The right foundation combines methodology, technology, and innovation. Joel recommends: A Distinct Strategic Account Management Methodology: This should include value co-creation and regular outcome validation, which differs from traditional sales playbooks. Enabling Technology: Use tools that collect and synthesize data from all touchpoints within both organizations, moving beyond spreadsheets to foster true alignment and prioritization. AI Integration: Those who ignore AI risk falling dangerously behind as it rapidly reshapes the landscape of business intelligence and process automation. Making the Key Account Plan a Living Strategy Joel details that effective plans are co-created with customers, regularly revisited, and focused on mutual priorities. Simple, actionable documentation, combined with technology for prioritization and measurement, transforms the plan from a once-a-year formality into a working blueprint for partnership. When confronted with real-life challenges such as price competition, don't just look for cost savings. Take a step back, engage a wider range of stakeholders, and solve bigger problems. That strategic lens is at the heart of lasting success in key accounts. Resources & People Mentioned Strategic Account Management Association Connect with Joel Schaafsma Joel Schaafsma on LinkedIn Connect With Paul Watts LinkedIn Twitter Subscribe to SALES REINVENTED Audio Production and Show Notes by PODCAST FAST TRACK https://www.podcastfasttrack.com
Some problem-solving wisdom comes from advanced frameworks. Other wisdom comes from eighth-grade science class. Eric Harding holds onto both. In this episode of People Solve Problems, host Jamie Flinchbaugh sits down with Eric Harding, Vice President of HR Operations and Systems at Republic Services. With more than twenty years across HR, manufacturing, and product development, Eric has seen what works, what fails, and what gets dressed up as something more sophisticated than it really is. The conversation moves through methodology, coaching, culture, and measurement, returning again and again to a single truth: the fundamentals do most of the work. Eric describes how his thinking about problem solving traces back through Intel's seven-step method in the early nineties, through Six Sigma belts and DMAIC, through Lean, and through more recent labels. He prefers the term methodology-based improvement because it removes the anxiety that surfaces the moment a specific brand name appears in the room. What he has noticed across organizations is that the named system matters less than the discipline of being systematic. And he is direct about where most teams fall short. Defining the problem clearly, he argues, is where the largest gains live, and it is also where most organizations are weakest. A story from early in his career illustrates how seriously he takes context. As a Lean manager overseeing multiple factories, Eric tried the same approach in two buildings sitting across the same parking lot. It thrived in one and failed in the other. Culture matters. The situation matters. He pairs this lesson with the situational leadership framework, reading both where the organization sits in its development and where the individual being coached sits in their understanding of problem-solving. The conversation turns to learning, where Eric makes the case for the A3 as a coaching surface that lets him see how someone thinks. He shares a moment from a strategy session with a shared service center team in Costa Rica, where nearly every problem statement returned by his teams contained the word manual. Eric now has a rule for his HR A3s. The word manual is not allowed in a problem statement because the moment it appears, the team has already decided that automation is the answer and has stopped thinking. He extends the same caution to artificial intelligence today, arguing that AI cannot rescue a process that has never been standardized in the first place. He also recounts a recent example where a team had spent years trying to solve what they believed was a roles and responsibilities problem. Once the process flow was mapped and the right questions were asked, the actual issue surfaced. Nobody was doing the work the same way. It was a process problem all along, and only the right kind of coaching brought that to the surface. On the subject of managing the problem landscape, Eric talks about the move from reactive firefighting to meaningful KPIs and monthly operating reviews. He shares the background check story, where loud complaints were shaping the narrative until a data analyst built the data set that showed the ninetieth percentile was on target and only the outliers were creating the noise. Data, he explains, lets you stop arguing and start solving. He encourages teams new to measurement to start somewhere, even imperfectly, and let the indicators mature over time so that operating reviews become a place for coaching and learning rather than reporting. To learn more about Eric Harding and his work, visit www.republicservices.com or connect with him on LinkedIn at www.linkedin.com/in/eric-harding-9627736.
Change Management Methods with Eva Lu-Boettcher, MD, FASA, FAAP
With MLS NEXT Cup kicking off later today, Jason caught up with Director of Methodology Javier Perez and U16 Head Coach Colby Childress to get updates on the teams away from the first team, their successes, and Childress' work with the U-16's to date...
The DOJ is intensifying its investigation into possible antitrust violations in the beef packing industry, and a federal judge in California has denied a request by the United Farm Workers to temporarily block the Trump administration's revised wage rule for H-2A workers.
To chill or not to chill? That is the question. And then a bunch more questions. Thankfully, author, winemaker, sommelier, and Enology expert, André Hueston Mack is on hand to explain Old World vs. New World wines, corks vs. caps, red, rosé, orange, and white wines, stemware, judging a wine by its label, the best glass of wine he's ever tasted, needless snobbery, aeration, decanting, and what those legs are doing dancing around your glass. Also: how to open a bottle with no corkscrew. Next week: how to make wine. Stay tuned. Visit André's website and follow him on Instagram and Threads Shop André's wines at Maison Noir Wines Buy his book, 99 Bottles: A Black Sheep's Guide to Life-Changing Wines, on Bookshop.org or Amazon Pre-order his upcoming book, Wine for Good Times: A Guide for Curious Drinkers, on Bookshop.org or Amazon (publishing February 23, 2027) A donation went to Food Bank for NYC More episode sources and links Other episodes you may enjoy: Zymology (BEER), Mixology (COCKTAILS), Ciderology (DELICIOUS APPLE BEVERAGES), Pomology (APPLES), Coffeeology (YEP, COFFEE), Fromology (CHEESE), Gastroegyptology (BREAD BAKING), Food Anthropology (FEASTS), Indigenous Cuisinology (NATIVE COOKING), Black American Magirology (FOOD, RACE & CULTURE), Melittology (BEES), Gustology (TASTE), Disgustology (REPULSION TO GROSS STUFF) 400+ Ologies episodes sorted by topic Smologies (short, classroom-safe) episodes Sponsors of Ologies Transcripts and bleeped episodes Become a patron of Ologies for as little as a buck a month OlogiesMerch.com has hats, shirts, hoodies, totes! Follow Ologies on Instagram and Bluesky Follow Alie Ward on Instagram and TikTok Editing by Mercedes Maitland of Maitland Audio Productions and Jake Chaffee Managing Director: Susan Hale Scheduling Producer: Noel Dilworth Transcripts by Aveline Malek Website by Kelly R. Dwyer Theme song by Nick Thorburn Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
We Need Your Support!
The memoirs of Paweł Z. Woś highlight the significant research challenges encountered by historians of the Intermarium area. Polish conspiracy during the German occupation, participation in the Warsaw Uprising, and operating a small business were all, in reality, acts of anti-communist resistance. The many omissions and instances of imprecision stem not only from the passage of time, but also from the carefully cultivated discretion imposed by the all-powerful communist secret police. For scholars, this represents a major challenge in the reconstruction of events and the discovery of historical truth. Dr. Sebastian Bojemski Graduated from the Institute of History of Warsaw University and gained his doctoral degree at The Cardinal Wyszyński University in Warsaw. At the Institute of World Politics (Washington, DC) he attended individual courses in geography and strategy, geoeconomy, strategic influence and propaganda. He was awarded scholarships by the Kosciuszko Foundation (USA) and the M. Grabowski Fund (UK). Mr Bojemski also has extensive experience in strategic communication, marketing, sales and management. For over 15 years (2003-2018) he had owned a Warsaw-based consulting firm. Between 2018-2024 he was an executive director for marketing at PKN Orlen – the largest oil company in Central Europe, a vice chairman at Lotos Fuels, the second largest oil company in Poland and a vice chairman at PERN, the largest fuel and logistics company in the region and critical infrastructure operator. He is currently affiliated with the University College of Professional Education as a member of the Center for Research on Disinformation and Cybersecurity and a senior fellow at the Eastern Flank Institute, a Brussels-based think tank. The Kościuszko Chair serves as a center for Polish Studies in the broadest sense, including learning, teaching, researching, and writing about Poland's culture, history, heritage, religion, government, economy, and successes in the arts, sciences, and letters, with special emphasis on the achievements of Polish civilization and its relation to other nations, particularly the United States. **Learn more about IWP graduate programs: https://www.iwp.edu/academics/graduate-degree-programs/ ***Make a gift to the IWP Kosciuszko Chair of Polish Studies: https://wl.donorperfect.net/weblink/WebLink.aspx?name=E231090&id=4
PMP Exam Mindset - Process Domain Task 13_ Determine project methodology
Martyn's process. Dealing with common trader pitfalls. Defining steps and methods for avoiding over-fitting."Opt My Strategy" the Robustness Testing Application built by Martyn Tinsley. Up to 25% off for Algo Advantage Subscribers!! https://www.algoadvantage.io/toolboxMartyn's paper on his new technique, "Walk Forward Correlation A Diagnostic for Over-Fitting and Structural Edge in Trading Strategy Optimisation": Our courses, community & toolbox: https://algoadvantage.ioContents:00:00 Introduction and Setup02:02 Martyn's Trading Journey12:07 Transition to Algorithmic Trading20:02 Common Pitfalls in Trading30:11 Developing Robust Trading Strategies31:55 Understanding Parameter Optimization and Performance Metrics39:43 The Impact of Economic News on Trading Strategies44:38 Identifying the True Edge of Trading Strategies52:05 Noise Reduction Techniques in Algorithmic Trading01:01:49 Research Phase vs. Optimization in Trading Strategies01:07:33 Reassessing Trading Strategies01:08:00 The Importance of Statistical Significance01:09:00 Understanding Sample Size in Trading01:10:00 Methodology for Backtesting Strategies01:11:59 The Role of Edge in Trading Strategies01:15:03 Randomness vs. Genuine Edge01:17:59 Long-Term Performance and Sample Size01:19:52 Confidence in Trading Results01:22:00 Increasing Sample Size for Better Results01:24:01 Testing Across Multiple Assets01:26:04 Optimizing Across Timeframes01:30:01 Generalizing Strategies Across Markets01:31:57 Diversification in Trading Strategies01:35:05 Final Thoughts on Strategy Optimization
Paris Marx is joined by Ben Tarnoff and Quinn Slobodian to discuss their new book Muskism which explores how Elon Musk exemplifies a new economic system shaping our lives, similar to Fordism in the twentieth century. Ben Tarnoff & Quinn Slobodian are the authors of Muskism. Ben is a writer and technologist based in Massachusetts and the author of Internet for the People. Quinn is professor of international history at Boston University, and the author of books like Crack-Up Capitalism. Tech Won't Save Us offers a critical perspective on tech, its worldview, and wider society with the goal of inspiring people to demand better tech and a better world. Support the show on Patreon. The podcast is made in partnership with The Nation. Production is by Kyla Hewson. Also mentioned in this episode: For listeners who are feeling extra academic, here is the Milton Friedman economics paper, “The Methodology of Positive Economics.” Quinn discusses his struggle to find any reporting on Jared Leto and the Optimus robot media stunt (that goes deeper than commenting on the virality).
In this episode of The Missing Secret Podcast, John and Kelly talk about taking the advanced leadership of self 12 minute a day methodology to the next level. Using AI. And here's the thing to appreciate. At the end the day, one success is determined by taking the right actions on a consistent basis. On the issue of consistently taking the right actions, that's addressed in the 12 minute day methodology. 95% of your daily actions are unconscious. When you feed the succinct articulation of your desired life yourself each day, that's the repetition the subconscious mind needs to rewire your autopilot. So you have control over those unconscious daily actions. That way you can do them consistently rather than sporadically.But here's the other issue. You have to be taking the right actions. So consider this. The right actions regarding your health are pretty straightforward. Regarding eating right and exercising. Same with having a great romantic relationship. The right actions are pretty straightforward. But when he gets to one's career, the right actions are not nearly as obvious. And in methodology, for your career you establish where you want your career to be three years from now. And the 4-5 milestones to get there. That gives you a guidepost for the right actions to take. But here's the problem. Your vision is trapped by the four walls of your own mind. Your vision of the right actions is constrained by your own biases and limited knowledge. But this can be overcome. And is being overcome using AI in the advanced leadership of self methodology. In this episode Kelly explains her three year vision for her business. As well as the three or four milestones to get there. Then once this is established, John and Kelly gives it all to chat GPT. Chat GPT then gives a much deeper view of the right actions. This overcomes one's limited vision from the four walls of one's own mind.Buy John's book, THE MISSING SECRET of the Legendary Book Think and Grow Rich : And a 12-minute-a-day technique to apply it here.About the Hosts:John MitchellJohn's story is pretty amazing. After spending 20 years as an entrepreneur, John was 50 years old but wasn't as successful as he thought he should be. To rectify that, he decided to find the “top book in the world” on SUCCESS and apply that book literally Word for Word to his life. That Book is Think & Grow Rich. The book says there's a SECRET for success, but the author only gives you half the secret. John figured out the full secret and a 12 minute a day technique to apply it.When John applied his 12 minute a day technique to his life, he saw his yearly income go to over $5 million a year, after 20 years of $200k - 300k per year. The 25 times increase happened because John LEVERAGED himself by applying science to his life.His daily technique works because it focuses you ONLY on what moves the needle, triples your discipline, and consistently generates new business ideas every week. This happens because of 3 key aspects of the leveraging process.John's technique was profiled on the cover of Time Magazine. He teaches it at the University of Texas' McCombs School of Business, which is one the TOP 5 business schools in the country. He is also the “mental coach” for the head athletic coaches at the University of Texas as well.Reach out to John at john@thinkitbeit.comLinkedIn: https://www.linkedin.com/in/john-mitchell-76483654/Kelly HatfieldKelly Hatfield is an entrepreneur at heart. She believes wholeheartedly in the power of the ripple effect and has built several successful companies aimed at helping others make a greater impact in their businesses and lives.She has been in the recruiting, HR, and leadership development space for over 25 years and loves serving others. Kelly, along with her amazing business partners and teams, has built four successful businesses aimed at matching exceptional talent with top organizations and developing their leadership. Her work coaching and consulting with companies to develop their leadership teams, design recruiting and retention strategies, AND her work as host of Absolute Advantage podcast (where she talks with successful entrepreneurs, executives, and thought leaders across a variety of industries), give her a unique perspective covering the hiring experience and leadership from all angles.As a Partner in her most recent venture, Think It Be It, Kelly has made the natural transition into the success and human achievement field, helping entrepreneurs break through to the next level in their businesses. Further expanding the impact she's making in this world. Truly living into the power of the ripple effect.Reach out to Kelly at kelly@thinkitbeit.comLinkedIn: https://www.linkedin.com/in/kelly-hatfield-2a2610a/Learn more about Think It Be It at https://thinkitbeit.com/LinkedIn: https://www.linkedin.com/company/think-it-be-it-llcFacebook: https://www.facebook.com/thinkitbeitcompanyThanks for listening!Thanks so much for listening to our podcast! If you enjoyed this episode and think that others could benefit from listening, please share it using the social media buttons on this page.Do you have some feedback or questions about this episode? Leave a comment in the section below!Subscribe to the podcastIf you would like to get automatic updates of new podcast episodes, you can subscribe to the podcast on Apple Podcasts or Stitcher. You can also subscribe in your favorite podcast app.Leave us an Apple Podcasts reviewRatings and reviews from our listeners are extremely valuable to us and greatly appreciated. They help our podcast rank higher on Apple Podcasts, which exposes our show to more awesome listeners like you. If you have a minute, please leave an honest review on Apple Podcasts.
Guest: Max Van Wyk De Vries, Assistant Professor at the University of CambridgeFrom wildfires sparking power outages, to hurricanes triggering chemical spills, today's disasters rarely unfold in isolation. They cascade, compound, and collide — creating challenges far more complex than any single hazard on its own. At the University of Cambridge, the Complex and Multihazard Research Group is leading the charge to better understand these interconnected risks, and to help communities, governments, and industries prepare for a more uncertain world. In this episode, we sit down with the program head of the group Max Van Wyk De Vries to explore how their research is reshaping the way we think about hazards, resilience, and the future of global risk.Chapters00:00 Understanding Complex and Multi-Hazard Risks10:47 The Role of Human Activity in Natural Hazards14:04 Break 119:24 Techniques and Methodologies in Hazard Research23:41 Break 229:24 Future Challenges and Opportunities in Multi-Hazard Risk ManagementSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Members of the Church of Jesus Christ of Latter-day Saints have received special undergarments as part of their temple endowment ceremonies since the days of Jospeh Smith. But what are these garments? How do they fit and feel? How have they changed with fashion trends over the years? And how do Latter-day Saints perceive and experience these garments as an embodied practice of their religion?Researchers Nancy Ross and Jessica Finnigan sit down with host Nicholas Shrum to discuss these and many other questions from their brand-new book (co-authored with Larissa Kanno Kindred) Mormon Garments: Sacred and Secret (University of Illinois Press). Having surveyed thousands of Latter-day Saints, Ross and Finnigan discuss their findings on the gendered difference in garment wearing, the ways in which garments make Mormonism feel embodied, the social costs of wearing — or not wearing — garments, the complexities of researching such a taboo topic, and the impact of these garments on the individual Latter-day Saints' relationship to the Church and God.Nancy Ross is an associate professor and the department chair of the Interdisciplinary Arts and Sciences Department at Utah Tech University. She was also a 2024 Clyde Research Fellow in Mormonism and Gender in the UVA Mormon Studies Prince Collection.Jessica Finnigan is the founder of Fractional Project Manager and a seasoned researcher and data analyst. She has been researching and writing about Mormonism — particularly the experience of Mormon women — for over a decade.
Daniel Laurison is a Professor of Sociology at Swarthmore College who focuses on class, social mobility, and racial inequality in US politics. He has recently released a report titled "The Political Disconnect: Working-Class and Low-Income People On What Politics Means to Them and How They Might be Mobilized." These citizens are not abstaining from voting because they are uninformed or apathetic. Rather, they think their vote does not matter and that politics is a game for wealthy elites. We talk about: Methodology of this qualitative study on political participation How voters perceive the connection between voting and tangible improvements in their lives Recommendations for politicians to engage in genuine two-way conversations with communities outside of election season Need to increase the number of working-class and low-income people in all aspects of politics, including working on campaigns, running for office, and local organizing #DanielLaurison #CampaignStrategy #PoliticalEngagement #WorkingClassVoters #LowIncomeVoters #Nonvoters #RelationalOrganizing #FieldStrategy #VoterContact #PoliticalInclusion #RepresentationMatters #ClassInPolitics #CivicEngagement #DigitalPolitics #CampaignProfessionals Strengthening Political Engagement Daniel Laurison
Beth Barnes and David Rein on the one graph that ate the AI timelines discourse, and why the two people who built it are the most careful about how you read it.**SPONSOR**Prolific - Quality data. From real people. For faster breakthroughs.https://www.prolific.com/?utm_source=mlstInterview: https://youtu.be/cnxZZTl1tkk---Beth Barnes and David Rein from METR on the one graph that ate the AI timelines discourse, and why the people who built it are the most careful about how it gets read.Beth founded METR after leaving OpenAI alignment. David is first author on GPQA and co-author on HCAST and the METR Time Horizons paper. Together they built the measurement Daniel Kokotajlo called the single most important piece of evidence on AI timelines: the log-linear line of "how long a task a frontier model can complete at 50% reliability" vs release date.The conversation opens on reward hacking. Current models can articulate in chat why a behaviour is undesired and then execute it anyway as agents. From there: construct validity, Melanie Mitchell's four-problem taxonomy, and the ARC-AGI 1-to-2 collapse as a worked example of adversarially-selected benchmarks regressing once labs target them. Beth's counter: METR deliberately does not adversarially select. David's: models do not have to do the right thing for the right reasons.Methodology, then specification — David's compiler analogy, Beth on four-month tasks as expensive to evaluate rather than unspecifiable. Then the SWE-bench reality check, the METR finding that half of passing PRs would not be merged, and Beth's horses-versus-bank-tellers analogy for the labour market.The close: monitorability, the coin-spinning boat, two-year recursive self-improvement, and Beth's line that "overhyped now" and "big deal later" are not correlated claims.---TIMESTAMPS:00:00:00 Intro00:02:06 Sponsor break: Prolific human-feedback infrastructure00:02:33 Welcome and the scalable oversight motivation00:06:02 Construct validity, benchmark pathologies and the Chollet worry00:15:45 Time Horizons: human time, HCAST tasks and the 50% logistic00:24:50 Is human difficulty really one variable?00:33:05 Agent harness evolution and the inference-compute dividend00:40:00 Scaffolding bells, token budgets and the credit-assignment problem00:44:15 Look at the damn graph: regularisation bug and reliability nuance00:50:00 Why 50%? Reliability, reward hacking and pizza-party transcripts00:55:20 Extrapolation risk and straight lines on graphs00:59:25 Software engineering as a specification acquisition problem01:07:40 Compilers also made ugly code: vibe-coding quality and Claude on METR Slack01:15:15 Strongest defensible claim, Carlini's compiler swarm and AI 202701:23:45 SWE-bench merge rates, the bank-teller analogy and horses01:31:45 Scheming, alignment faking and the mentalistic vocabulary problem01:40:45 Reward hacking, monitorability and chain-of-thought faithfulness01:45:25 Recursive self-improvement, knowledge vs intelligence and closingReScript: https://app.rescript.info/public/share/de3bb40cc02ee39fdf36e2c60366eb4d(PDF, refs, transcript etc)
Jim Harold returns to the show to talk about his latest book and tell us some ghost stories. Jim's latest collection is True Ghost Stories; Jim Harold's Campfire 3. 70 Stories in this one, of all kinds, not just ghosts. In 2005, Jim created The Paranormal Podcast. After over a decade of working on the business side of media, Jim decided it was time to dust off his broadcast training and step back behind the mic. A life long interest in the paranormal, combined with his love of broadcasting and technology, resulted in some the most successful podcasts of their type to date. Jim has worked in radio, business to business media and has written, hosted and produced award winning video programming over the course of his career. He holds a Master's Degree in Applied Communication Theory and Methodology and is accredited as a Certified Digital Media Consultant by the Radio Advertising Bureau. Jim has also had the opportunity to teach at the university level. Jim Harold's website is JimHarold.com Hosted on Acast. See acast.com/privacy for more information.
Every analyst, every think tank, every consulting deck has an opinion on AI's water footprint (and overall on AI and Water)But nobody bothered to ask the people actually watching the videos, posting the comments, and shaping the narrative. You'd need to be mad to do that, right?So I read 2,540 of them.
We have Daniel Schlagwein on the show, who is what Germans call a "Tausendsassa:" He is both a practitioner and researcher of digital nomadism, the editor-in-chief of the Journal of Information Technology, and president of the AIS special interest group on Grounded Theory Methodology. We touch upon all three of these aspects, but at the core we want to know from Daniel whether generative AI tools are automating grounded theory and thereby eliminate what used to be at the heart of a humanistic and constructionist approach to doing research – or are they merely leveling the playing field for qualitative field researchers by giving them computational support matching those tools that quantitative researchers have had for a long time. Daniel argues that it depends on the specific flavor of the grounded theory method you are using to determine whether and how you can leverage generative AI for such research. References Wang, B., Schlagwein, D., Cecez-Kecmanovic, D., & Cahalane, M. C. (2025). 'Emancipation' in Digital Nomadism vs in the Nation‑State: A Comparative Analysis of Idealtypes. Journal of Business Ethics, 198(1), 35–68. Hoffman, P. (1998). The Man Who Loved Only Numbers. Hyperion Books. Garland, A. (1996). The Beach. Viking. Jiwasiddi, A., Schlagwein, D., Cahalane, M. C., Cecez-Kecmanovic, D., Leong, C., & Ractham, P. (2024). Digital Nomadism as a New Part of the Visitor Economy: The Case of the 'Digital Nomad Capital' Chiang Mai, Thailand. Information Systems Journal, 34(5), 1493–1535. Fromm, E. (1941). Escape from Freedom. Farrar & Rinehart. Glaser, B. G., & Strauss, A. L. (1967). The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine Publishing Company. Glaser, B. G. (1978). Theoretical Sensitivity: Advances in the Methodology of Grounded Theory. Sociology Press. Strauss, A. L., & Corbin, J. (1998). Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory (2nd ed.). Sage. Charmaz, K. C. (2014). Constructing Grounded Theory: A Practical Guide through Qualitative Analysis (2nd ed.). Sage. Nelson, L. K. (2020). Computational Grounded Theory: A Methodological Framework. Sociological Methods & Research, 49(1), 3–42. Gopal, R., Li, J., Riemer, K., Sarker, S., Singh, P. V., Susarla, A., Bichler, M., & Thatcher, J. B. (2025). Inventing with Machines: Generative AI and the Evolving Landscape of IS Research. Information Systems Research, 36(4), 1949–1967. Zhou, Y., Yuan, Y., Huang, K., & Hu, X. (2024). Can ChatGPT Perform a Grounded Theory Approach to Do Risk Analysis? An Empirical Study. Journal of Management Information Systems, 41(4), 982–1015. Yue, Y., Liu, D., Lv, Y., Hao, J., & Cui, P. (2025). A Practical Guide and Assessment on Using ChatGPT to Conduct Grounded Theory: Tutorial. Journal of Medical Internet Research, 27, e70122. Wiesche, M., Jurisch, M., Yetton, P., & Krcmar, H. (2019). Grounded Theory Methodology in Information Systems Research. MIS Quarterly, 41(3), 685–701. Sarker, S., Xiao, X., Beaulieu, T., & Lee, A. S. (2018). Learning from First-Generation Qualitative Approaches in the IS Discipline: An Evolutionary View and Some Implications for Authors and Evaluators (PART 1/2). Journal of the Association for Information Systems, 19(8), 752–774. AIS Special Interest Group on Grounded Theory Methodology (SIG GTM): https://aisnet.org/members/member_engagement/groups.aspx?code=SIGGTM. Recker, J., Zeiss, R., & Mueller, M. (2024). iRepair or I Repair? A Dialectical Process Analysis of Control Enactment on the iPhone Repair Aftermarket. MIS Quarterly, 48(1), 321–346.
The UTMB Index and race scores have become increasingly significant in the global trail running ecosystem. The Index upstream of sponsorship and race entry opportunities for pros, it allows fans to gauge who is performing best on the world's stage, and it helps media members contextualize performances across years, distances, and different course terrains. Today the UTMB Index is evolving in some subtle yet important ways. Joining me to talk all about it are Adrian Vincentand Karen Merlin — two members of the team who worked on this new system and are well qualified to explain how things are changing and what it means for the sport. Timestamps: 00:00 – Intro + episode overview (UTMB Index) 00:50 – Guest introductions (Adrian Vincent & Karen Merlin) 02:50 – Why the UTMB Index was created 07:25 – Why the index matters for the sport 10:45 – Index vs. race scores explained 13:40 – What the index is (and isn't) 15:45 – Why changes were needed 19:40 – Gender scoring discussion 24:40 – Myth: bias toward UTMB races 26:15 – Challenge of collecting global race results 30:55 – Myth: weather/conditions affect scores 37:15 – New scoring system overview 39:25 – Step 1: Finding similar races 42:40 – Step 2: Expected score + confidence 47:45 – Step 3: Selecting high-quality data 51:20 – Step 4: Final calculation (regression explained) 55:05 – Retroactive re-scoring (what changes) 56:10 – Impact on everyday runners 57:10 – Impact on elite athletes + qualification 58:55 – Myth: bad races hurt your index 01:00:55 – Highest scores ever (new system) 01:06:10 – Behind the scenes of the rebuild 01:09:00 – Transparency + final thoughts 01:10:30 – Closing remarks Additional Material: Educational video: "How my UTMB Index is calculated" Methodology note General public article REGISTER FOR TRAILCON - https://trailconference.com/ Sponsors: Use code FREETRAIL25 for 25% off your first order of NEVERSECOND nutrition at never2.com Check out the Capilene Cool Sun Hoodie from Patagonia Use code FREETRAIL for an extra discount on Clearlight Saunas at HealWithHeat.com Use this link for 30% off Ketone-IQ Freetrail Links: Website | Freetrail Pro | Patreon | Instagram | YouTube | Freetrail Experts Dylan Links: Instagram | Twitter | LinkedIn | Strava
Jack Chambers-Ward and Mark Williams-Cook are back in the Candour studio to discuss if People Also Ask questions improve rankings and Google's recent crackdown on self-promotional listicles.Sponsored by TrendosNo demo required. No paywall. Free plan available.Check your brand's AI visibility now → Trendos.comThey discuss a Chris Green study using AlsoAsked API, SERP scraping, and OpenAI to score whether top-20 ranking pages fully/partially answer related People Also Ask questions, finding a strong correlation in the top five positions, strongest for commercial/transactional queries and weaker for informational/navigational.The conversation shifts to geographic personalisation in search and AlsoAsked's city-based selector, plus upcoming talks referencing regional question differences. They then cover major traffic losses seen around late January for sites relying on self-promotional “best X” listicles and programmatic comparison pages, noting some core product pages survived while other pages were suppressed.Chris Green's AlsoAsked study:https://alsoasked.com/insights/paa-ranking-correlation https://www.youtube.com/watch?v=_9dfEjlmZx0 Time stamps00:00 Introduction01:18 Back in the studio with Mark02:48 PAA study setup06:03 Methodology and scoring08:10 Why commercial queries win11:58 Regional PAA insights16:40 Sponsor: Trendos20:39 Listicle crackdown begins23:37 Self promo listicles26:15 Traffic drop fallout28:57 Honesty beats hype31:25 Gemini warning cards34:17 No awards strategy37:37 Fan out award signals41:56 Wrap up and upcoming events
The Wheel Strategy is often touted as the ultimate "income generator," but most traders get it wrong because they lack the right mindset. In this episode, Mark Longo is joined by Dan Passarelli to discuss his brand-new book, Build Consistent Wealth with Options. They go beyond the basic mechanics to explore the three pillars of the Wheel, why most retail traders fail when they actually get assigned, and how to "rewire your brain" for probabilistic investing. Whether you're a passive investor or an active trader looking for an edge, this deep dive into the "Cycle-Recycle" method will change how you view covered calls and cash-secured puts forever. In this episode, we cover: The Three Pillars: Mindset, Objectives, and Methodology. The "Cycle-Recycle" Trade: Why the Wheel only works as a continuous system. The "Skate" vs. "Trade" Objective: How to decide if you actually want the stock. The PAS Indicator: Dan's custom tool for finding the "sweet spot" in premium. Alpha & Taxes: Maximizing your edge while managing the "silent killers" of wealth.
The Wheel Strategy is often touted as the ultimate "income generator," but most traders get it wrong because they lack the right mindset. In this episode, Mark Longo is joined by Dan Passarelli to discuss his brand-new book, Build Consistent Wealth with Options. They go beyond the basic mechanics to explore the three pillars of the Wheel, why most retail traders fail when they actually get assigned, and how to "rewire your brain" for probabilistic investing. Whether you're a passive investor or an active trader looking for an edge, this deep dive into the "Cycle-Recycle" method will change how you view covered calls and cash-secured puts forever. In this episode, we cover: The Three Pillars: Mindset, Objectives, and Methodology. The "Cycle-Recycle" Trade: Why the Wheel only works as a continuous system. The "Skate" vs. "Trade" Objective: How to decide if you actually want the stock. The PAS Indicator: Dan's custom tool for finding the "sweet spot" in premium. Alpha & Taxes: Maximizing your edge while managing the "silent killers" of wealth.
This week, I'm joined by Jermaine Jones, visionary founder of Jones Global Group and a recognized leader in enterprise risk and strategic talent selection. Jermaine shares his insights on common pitfalls sales professionals encounter during account transitions, and gives actionable strategies for aligning account plans with customer objectives. We also discuss his favorite tools and methodologies for key account managers and why he believes that stakeholder mapping is a crucially important part of the process. Outline of This Episode [00:00] Key Account vs. Regular Account [01:26] Common mistakes organizations make in defining key accounts [02:45] Importance of diagnosis before prescription in consultative selling [03:31] Use of a closed loop system and Ansoff Matrix [04:39] How to tailor communication for different decision-makers [06:16] 4D task prioritization tool [12:04] Finding a Zone of Possible Agreement (ZOPA) to protect margins and reduce risk Moving Beyond Revenue Organizations often misclassify accounts by prioritizing revenue rather than focusing on profit or the return on time invested. Jermaine references the Pareto Principle, the well-known 80/20 rule, and explains that "80% of your profitable sales come from 20% of your customers". A key account isn't simply about large volume; it's an account where your domain expertise fundamentally shifts the client's profitability. To identify strategic partners, sales leaders have to calculate return on time invested and examine how their influence impacts the client's bottom line. Without this, accounts remain routine and are a missed opportunity for strategic growth. Rethinking Relationship Management Transitioning from a transactional sales approach to effective key account management is fraught with pitfalls. The most common mistake is staying stuck in a perpetual "hunter" mindset. Salespeople fail because they skip the prescription before the diagnosis." The sales process is a little like medicine, where selling becomes 'malpractice' if you pitch solutions before properly understanding the client's needs via thorough discovery. The path to success lies in shifting focus. Account managers should embrace a consultative approach, building trust and acting as advisors rather than mere vendors. Aligning with Client Objectives Jermaine recommends using closed-loop goal execution and the Ansoff Matrix to identify opportunities for market penetration and product development. He emphasizes aligning one's talent and resource supply chain to support the client's expansion and adapt quickly as objectives evolve. Critical to this approach is ensuring plans are dynamic—active tools shaped by real-time feedback and shifting environments rather than static documents filed away and forgotten. Effective plans rely on the 70/20/10 development model, so you're continuously adapting based on 70% real-world experience and market feedback. The Power of Stakeholder Mapping Stakeholder mapping prevents communication style bias, for instance, pitching with enthusiasm to a data-driven CFO is a sure way to lose trust if the presentation lacks concrete analysis. To gain access to senior decision makers, authority and social proof are key: bringing rigorous, certified data positions the seller as an invaluable source of insight rather than a time-waster. Essential Tools and Methodologies for Key Account Managers According to Jermaine, what sets top account managers apart is mastery of three things. First, understanding and employing the five pillars of sales success, with particular emphasis on self-awareness and domain expertise. Technology and AI are no substitute for deep industry knowledge. Second, the 4D task tool prioritization (Do it, Delegate, Date, Delete) ensures efficiency does not replace effectiveness—the real goal is to do the right things, not just do things right. Third, value-based motivation statements open every executive interaction with a clear, credible promise, establishing technical trust and ensuring every conversation is purposeful. Resources & People Mentioned The Pareto Principle Ansoff Matrix Connect with Jermaine Jones Jermaine Jones on LinkedIn Connect With Paul Watts LinkedIn Twitter Subscribe to SALES REINVENTED Audio Production and Show Notes by PODCAST FAST TRACK https://www.podcastfasttrack.com
The Director of Methodology for Atlanta United, Javier Perez, visits SDH AM to give an update on the Academy and ATLUTD2 recent successes as well as look at the purpose of methodology in the franchise and the challenges- adding recent context to the work done below the first team level.
Featuring a slide presentation and related discussion from Dr Seth Wander, including the following topics: Biological impact of clinically relevant biomarkers (eg, ESR1 mutations, PIK3CA/AKT1/PTEN alterations) (0:00) Methodologies for biomarker assessment in clinical practice: Tissue versus liquid biopsy (5:21) Methodologies for biomarker assessment in clinical practice: Novel platforms (13:56) Appropriate timing for assessment of ESR1 and PI3K pathway alterations (17:34) Evolving guidelines for routine biomarker evaluation (21:37) Implications of precision oncology clinical trials for future biomarker utility (25:07) Summary, key questions, future directions (33:09) CME information and select publications
Author Han Zhang discusses the article, "Joint Text-and-Image Clustering for Social Science Research" published in the February 2026 issue of Sociological Methodology.
Closed Loop Sales Strategy: Why Most B2B Teams Are Getting It WrongMost B2B teams are still chasing meetings, pipeline, and MQLs—without ever understanding if a buyer is actually ready to buy.In this episode, we join Kieran Longhurst to break down the Closed Circuit Selling Strategy —why traditional sales models are failing, and how to fix them.We unpack how sales should really work, why booking meetings is the wrong goal, and how cataloguing your market creates a feedback loop across marketing, sales, product, and leadership.This isn't about selling harder. It's about building a system that aligns with how buyers actually make decisions.Tune in and learn:Why focusing on “meetings booked” is killing your pipelineHow to use sales conversations as real market intelligenceThe exact method to sell on your buyer's timelineIf you're a B2B marketer or revenue leader trying to drive real pipeline—not just activity—this episode will completely change how you think about sales.SUBSCRIBE to our channel: https://www.youtube.com/@theb2bplaybook SUBSCRIBE to our newsletter: https://theb2bplaybook.com/newsletter/ GET the latest CONTENT: https://theb2bplaybook.com/00:00 Why Most B2B Sales Strategies Are Broken 01:00 The 95% Problem: Why You're Only Talking to Buyers 02:00 The Real Sales Mindset (That No One Teaches) 03:00 Why “Sell Me This Pen” Is the Wrong Model 05:00 Architecture vs Tactics: The Core Shift 07:00 Why Relationship Building Is Misunderstood 09:00 What Sales Actually Is (And Why Most Get It Wrong) 11:00 The Hidden Cost of Booking Bad Meetings 13:00 The Cataloguing Method Explained 15:00 Why Most Sales Teams Waste 90% of Their Effort 18:00 How to Use Sales as Real Market Research 20:00 The Feedback Loop That Fixes Marketing 23:00 Why Founders Forget How They Originally Sold 27:00 The Death of the “Scale Fast” Sales Model 30:00 Human Selling vs Automated Outreach 33:00 How to Actually Get Buyers to Share Information 38:00 Real Examples: Closing Enterprise Deals with LinkedIn 45:00 Why MQLs Destroy Marketing Teams 50:00 The Smartest Prospecting Tactic We've Seen 55:00 AI, Search, and the Future of Sales 59:00 Final Takeaways: Rapport Over Relationships
I chat with Jannik Kaiser about regenerative evaluation, an approach that asks how evaluation itself can contribute to flourishing. We discussed Jannik's background in evaluation and what led him to regenerative evaluation, how and why the approach was developed, what regenerative evaluation is and an example of regenerative evaluation in practice, and more. "Too often, evaluation is experienced as a "tax" on doing good: an extractive exercise where we mine data from communities to feed upward reporting structures. It reinforces a power dynamic where the funder holds the yardstick and the community bears the burden of proof. We count the fruits while depleting the soil. But I believe - and have witnessed first hand - that evaluation can be a source of vitality and justice, not just accountability." - Regenerative Evaluation Living Paper: Influences, Pathways, & Practices Resources Introduction to the Regenerative Evaluation Living Paper Regenerative Evaluation Living Paper: Influences, Pathways, & Practices Impact Garden M&E in Complexity: Presenting a methodology for making credible claims Capacity Compass Regenerative Evaluation Community of Practice About Jannik Kaiser Jannik Kaiser is the Co-founder and CEO of Unity Effect, where he leads the area of Regenerative Measurement and Evaluation. As the main editor of the Regenerative Evaluation Living Paper, Jannik has dedicated his career to bridging complexity science with participatory practice. He advocates for transforming evaluation from a compliance-driven reporting requirement into a regenerative intervention in itself: one that gives more energy than it takes and actively shifts institutional power. His work encompasses a broad spectrum of contributions, ranging from advising global organizations such as the ILO and UN agencies, to developing open-source frameworks such as the Impact Garden, Capacity Compass, and Methodology for Credible Claims in Complexity, to empower purpose-driven organizations worldwide. Email: jannik@unityeffect.net LinkedIn: https://www.linkedin.com/in/jannik-kaiser/
My guest this week, Josh Curcio, is CRO and partner at Protocol 80, a HubSpot community champion, and experienced strategist for technical B2B companies. We dig into key account management—exploring what differentiates key accounts from regular ones, common mistakes salespeople make when transitioning to account management, and strategies for aligning sales approaches with customers' business objectives. Josh shares his expertise on stakeholder mapping, the importance of regular check-ins, and actionable tips for building lasting relationships. Tune in for practical advice as he shares how key account managers can avoid the pitfalls of overpromising and how to ensure account plans stay relevant even when plans change. Outline of This Episode [00:00] Lessons and tools for outstanding key account management [02:27] Differences in mindset and approach between sales and account management [04:26] The importance of stakeholder mapping for successful key account management [06:07] Top tools for managing accounts [07:51] Importance of using a CRM [09:06] How do we make a key account plan a living document? [12:37] Building trust and managing expectations [15:04] Josh's real-world new product launch strategy Mastering Key Account Management Not all clients or accounts wield the same influence over your business's trajectory. Key accounts are typically those representing a significant portion of revenue or strategic value. Losing one can deliver a substantial blow, while regular accounts—though important—don't carry quite the same weight. The challenge for many organizations is clarity: few actually pause to set objective parameters for what constitutes a key account, relying instead on vague impressions. To move forward, businesses must formalize criteria, such as annual revenue thresholds or multi-service engagement, creating a blueprint for strategic focus. Avoiding Common Account Management Pitfalls Transitioning from sales to account management demands a shift in mindset. One of the biggest mistakes is only appearing when there's an agenda to sell. It undermines trust and feels transactional, leaving clients unsupported in their day-to-day operations. Instead, key account managers should prioritize ongoing communication, shaping relationships that transcend the sales cycle. This regular presence builds credibility and ensures clients feel valued, not just targeted. A robust key account strategy hinges on aligning with the client's business objectives. This starts with scheduled, purposeful meetings, often in the form of Quarterly Business Reviews (QBRs) that dig into overarching goals and challenges. These sessions aren't just check-ins, they're opportunities to uncover future objectives and strategize collaborative pathways. The ritual of regular reviews ensures nothing falls off the radar and demonstrates a commitment to shared success. Tools, Technologies, and Methodologies for Account Managers Modern key account management relies on leveraging technology to keep relationships alive and plans actionable. Josh recommends three essentials: CRM Systems: Platforms like HubSpot consolidate organizational knowledge, contact history, and stakeholder mapping, ensuring continuity if an account manager moves on. AI Note Takers: Tools such as Ask Elephant automate meeting documentation, sentiment analysis, and risk detection, feeding insights directly into the CRM. Structured Check-ins: Regular, process-driven meetings should be documented and tracked within the CRM so action items and objectives aren't forgotten. Growing a Strategic Account Josh shares a story of a client launching a new product. Rather than simply reallocating existing capacity, he transparently mapped client objectives and recommended increased investment to avoid undermining the main brand, resulting in a larger retainer and a stronger partnership. Listen, communicate honestly, and tie recommendations directly to the client's ambition. Key account management is not just about maintaining revenue streams—it's about creating strategic alliances that propel both companies forward. Resources & People Mentioned Ask Elephant Hubspot Connect with Josh Curcio Joshua Curcio on LinkedIn Connect With Paul Watts LinkedIn Twitter Subscribe to SALES REINVENTED Audio Production and ShowNotess by PODCAST FAST TRACK https://www.podcastfasttrack.com
This episode features listener takeaways from the recent RootsTech 2026 conference. Diana discusses the overall positive impressions of the event, noting the high quality of the presentations and the unanimous message about disclosing the use of AI and double-checking its work. Nicole and Diana review several classes on AI, including transforming family history into song, understanding AI's role in archival stewardship, and mastering the basics of AI for genealogy. They share lessons on using AI to abstract information from records, create citations, and analyze research logs to identify gaps. Diana also discusses her class on using AI to clarify complex court records by translating obsolete terms and organizing chronological data. The hosts share insights on specialized research areas, methodology, and records. Diana highlights classes on DNA, including using shared-match grids to analyze and group DNA matches and a methodology to defeat the "Genealogy Gremlin" by evaluating match pedigrees and mitigating confirmation bias. They share a listener's review of Michael Lacopo's session on how to successfully approach non-responsive cousins to encourage them to share their DNA. The hosts discuss classes on research methodology, such as resolving same-name issues by building identity profiles and constructing timelines, and using genealogical analysis to solve conflicting birth dates. Diana notes that a class on probate files reveals that these records contain many rich documents beyond the will, offering clues about an ancestor's associates and lifestyle. They also share Sue Taylor's review a class on Italian records that explains the Latin grammatical forms—nominative, genitive, and accusative—found in civil and parish records. Listeners learn how to access recordings and handouts from RootsTech to apply new AI tools to their research, master advanced DNA analysis techniques, and apply genealogical proof standards to complex records and challenging research questions. This summary was generated by Google Gemini. Links to RootsTech Classes RootsTech Classes in the On-Demand Library - https://www.familysearch.org/en/rootstech/library Even if there's no recording, you can always review the handout! AI and Genealogy ● Musical Memories - Transforming Family History into Song with AI (recorded) by Brandon Camp of Storied - https://www.familysearch.org/en/rootstech/session/musical-memories-transforming-family-history-into-song-with-ai ● Preserving the Past with Emerging Tech: AI's Role in Archival Stewardship (recorded) by Bret Weekes, John Morrey, John Alexander, Jimmy Zimmerman - https://www.familysearch.org/en/rootstech/session/preserving-the-past-with-emerging-tech-ais-role-in-archival-stewardship ● Your AI Toolkit: Essential Tools for Family History Success (recorded) by Laryn Brown - https://www.familysearch.org/en/rootstech/session/your-ai-toolkit-essential-tools-for-family-history-success ● AI & Family History: Foundations & First Steps: Mastering AI Basics for Genealogy (recorded) by Steve Little - https://www.familysearch.org/en/rootstech/session/ai-family-history-foundations-first-steps-mastering-ai-basics-for-genealogy ● FamilySearch for Latinos: Using AI to Grow Your Tree (recorded) by Ada Luque Nelson - https://www.familysearch.org/en/rootstech/session/familysearch-for-latinos-using-ai-to-grow-your-tree ● FamilySearch Full-Text Search – Your Golden Path to Ancestral Discovery (recorded) by David Ouimette - https://www.familysearch.org/en/rootstech/session/familysearch-full-text-search-your-golden-path-to-ancestral-discovery ● AI-Powered Research Logs: From Chaos to Clarity in Your Genealogy Data (recorded - not online yet) by Diana Elder - https://www.familysearch.org/en/rootstech/session/ai-powered-research-logs-from-chaos-to-clarity-in-your-genealogy-data ● From Complex to Clear: Transform Court Records with AI Tools [in-person only] by Diana Elder - https://www.familysearch.org/en/rootstech/session/from-complex-to-clear-transform-court-records-with-ai-tools ● The Future of AI in Genealogy (recorded) by David Ouimette, Steve Little, Diana Elder, Mark Thompson, Dave Vance - https://www.familysearch.org/en/rootstech/session/the-future-of-ai-in-genealogy ● DNA Evidence Analysis with AI (recorded) by Nicole Dyer - https://www.familysearch.org/en/rootstech/session/dna-evidence-analysis-with-ai DNA ● Using Shared-Match Grids and Matrices In Your Family History Research [in-person only] by Jonny Perl - https://www.familysearch.org/en/rootstech/session/using-shared-match-grids-and-matrices-in-your-family-history-research ● DNA Swim School: 1-3. Diahan Southard. Shared matches. (recorded) by Diahan Southard - https://www.familysearch.org/en/rootstech/session/dna-swim-school-part-1-floating-with-one-dna-match ● Using Autosomal DNA Analysis to Identify an Ancestor's Likely Parents (recorded) by Alice Childs - https://www.familysearch.org/en/rootstech/session/using-autosomal-dna-analysis-to-identify-an-ancestors-likely-parents ● DNA Analysis Methodology: Defeat the Genealogy Gremlin (recorded) by Karen Stanbary - https://www.familysearch.org/en/rootstech/session/dna-analysis-methodology-defeat-the-genealogy-gremlin ● Hi, We're Related! Successful Communication With Your DNA Matches [in-person only] by Michael Lacopo - https://www.familysearch.org/en/rootstech/session/hi-were-related-successful-communication-with-your-dna-matches Methodology ● Genealogical Proof in Practice: Resolving Conflicts and Building Sound Conclusions [in-person only] by D. Joshua Taylor - https://www.familysearch.org/en/rootstech/session/genealogical-proof-in-practice-resolving-conflicts-and-building-sound-conclusions ● The GPS in Practice: Examples of Reasonably Exhaustive Research (recorded) by Angela Packer McGhie - https://www.familysearch.org/en/rootstech/session/the-gps-in-practice-examples-of-reasonably-exhaustive-research ● When Nothing Found Means Something: Negative Search Results vs. Negative Evidence (recorded) by Diana Elder - https://www.familysearch.org/en/rootstech/session/when-nothing-found-means-something-negative-search-results-vs-negative-evidence ● Untangling the Darling Web: Advanced Strategies for Same Name Resolution (recorded) by Bonnie Wade Mucia - https://www.familysearch.org/en/rootstech/session/untangling-the-darling-web-advanced-strategies-for-same-name-resolution ● Which Date Is Right? Solving Birthdate Conflicts Through Genealogical Analysis (recorded) by Carolynn Ladd - https://www.familysearch.org/en/rootstech/session/which-date-is-right-solving-birthdate-conflicts-through-genealogical-analysis Records and Sources ● Taxes & Tithes: Researching Enslaved Communities in Colonial Virginia [in-person only] by Orice Jenkins - https://www.familysearch.org/en/rootstech/session/taxes-and-tithes-researching-enslaved-communities-in-colonial-virginia ● Double Dates and Lost Days: Making Sense of the Calendar Switch [in-person only] by Seema Kenney - https://www.familysearch.org/en/rootstech/session/double-dates-and-lost-days-making-sense-of-the-calendar-switch ● Indentured Servitude: Michael Brophy. Where to search for information. [in-person only] by Michael Brophy - [URL is missing] ● Cards, Clevises, and Calomel: What Probate Files Can Reveal about Our Ancestors (recorded) by Nancy Peters - https://www.familysearch.org/en/rootstech/session/cards-clevises-and-calomel-what-probate-files-can-reveal-about-our-ancestors ● Provenance & Proof: Advanced Strategies for Finding and Using Manuscripts In Your Research (recorded) by Kelly Richardson - https://www.familysearch.org/en/rootstech/session/provenance-proof-advanced-strategies-for-finding-and-using-manuscripts-in-your-research Geographic & Ethnic Research ● Civil and Parish Records in Italy: From the Council of Trent to the 20th Century. (recorded) by Daniel Taddone - https://www.familysearch.org/en/rootstech/session/civil-and-parish-records-in-italy-from-the-council-of-trent-to-the-20th-century ● New Adventures in the Americas: Colonial research like never before [in-person only] by Kristilee J. Manuel - https://www.familysearch.org/en/rootstech/session/new-adventures-in-the-americas-colonial-research-like-never-before ● Mastering the Four Prongs of Onsite Genealogy Research [in-person only] by Michael D. Lacopo - https://www.familysearch.org/en/rootstech/session/mastering-the-four-prongs-of-onsite-genealogy-research Sponsor – Newspapers.com For listeners of this podcast, Newspapers.com is offering new subscribers 20% off a Publisher Extra subscription so you can start exploring today. Just use the code "FamilyLocket" at checkout. Research Like a Pro Resources Airtable Universe - Nicole's Airtable Templates - https://www.airtable.com/universe/creator/usrsBSDhwHyLNnP4O/nicole-dyer Airtable Research Logs Quick Reference - by Nicole Dyer - https://familylocket.com/product-tag/airtable/ Research Like a Pro: A Genealogist's Guide book by Diana Elder with Nicole Dyer on Amazon.com - https://amzn.to/2x0ku3d 14-Day Research Like a Pro Challenge Workbook - digital - https://familylocket.com/product/14-day-research-like-a-pro-challenge-workbook-digital-only/ and spiral bound - https://familylocket.com/product/14-day-research-like-a-pro-challenge-workbook-spiral-bound/ Research Like a Pro Webinar Series - monthly case study webinars including documentary evidence and many with DNA evidence - https://familylocket.com/product-category/webinars/ Research Like a Pro eCourse - independent study course - https://familylocket.com/product/research-like-a-pro-e-course/ RLP Study Group - upcoming group and email notification list - https://familylocket.com/services/research-like-a-pro-study-group/ Research Like a Pro Institute Courses - https://familylocket.com/product-category/institute-course/ Research Like a Pro with DNA Resources Research Like a Pro with DNA: A Genealogist's Guide to Finding and Confirming Ancestors with DNA Evidence book by Diana Elder, Nicole Dyer, and Robin Wirthlin - https://amzn.to/3gn0hKx Research Like a Pro with DNA eCourse - independent study course - https://familylocket.com/product/research-like-a-pro-with-dna-ecourse/ RLP with DNA Study Group - upcoming group and email notification list - https://familylocket.com/services/research-like-a-pro-with-dna-study-group/ Thank you Thanks for listening! We hope that you will share your thoughts about our podcast and help us out by doing the following: Write a review on iTunes or Apple Podcasts. If you leave a review, we will read it on the podcast and answer any questions that you bring up in your review. Thank you! Leave a comment in the comment or question in the comment section below. Share the episode on Twitter, Facebook, or Pinterest. Subscribe on iTunes or your favorite podcast app. Sign up for our newsletter to receive notifications of new episodes - https://familylocket.com/sign-up/ Check out this list of genealogy podcasts from Feedspot: Best Genealogy Podcasts - https://blog.feedspot.com/genealogy_podcasts/
ANGELA'S SYMPOSIUM 📖 Academic Study on Witchcraft, Paganism, esotericism, magick and the Occult
What if everything you thought you knew about Solomonic magic was wrong? In this video, I explore Gal Sofer's groundbreaking study of Solomonic magic and why it changes the way we understand the Key of Solomon, the Goetia, and the wider grimoire tradition. Far from being a single, unified body of ancient magical wisdom, these texts emerge as a fluid network shaped by scribes, translations, and centuries of adaptation across Jewish, Christian, Arabic, Greek, and Latin traditions.We will look at the real history behind Solomonic texts, the myth of the “original” grimoire, the Jewish roots of demon-summoning traditions, and why this matters not only for scholars of Western esotericism but also for contemporary practitioners. If you are interested in grimoires, ceremonial magic, the Key of Solomon, the Lesser Key, or the history of Western occultism, this episode will give you a much deeper understanding of what is really at stake.CONNECT & SUPPORT
Jason Longshore and Madison Crews sit down with Atlanta United Director of Methodology Javier Pérez for a deep look at what the club is building in its academy. Pérez discusses staffing, training structure, nutrition, player mentality, and how Atlanta United is trying to define a clearer football identity across its pathway.
Send us Fan MailHow do business owners scale beyond themselves?
We Need Your Support!
Briefing Document: Themes and Insights from "The Spirit of the Honey Badger" Executive Summary The source material explores the concept of spiritual readiness through the lens of the Apostle Paul's final exhortations in 2 Timothy. The central thesis posits that while individuals—particularly men—are naturally wired to prepare for physical threats (symbolized by the "honey badger" or "Rottweiler"), they are often woefully unprepared for spiritual challenges. The document outlines three critical takeaways: The Political Nature of the Gospel: In the first-century Roman context, the "Good News" (euangelion) was a subversive political statement identifying Jesus, not Caesar, as the true King. The Believer as the "Rescue Plan": The mission of the church is not localized to the clergy but is the responsibility of individual believers who encounter people in crisis in their daily lives. A Framework for Preparation: Spiritual readiness is achieved through identifying one's purpose, engaging in communal accountability ("circles, not rows"), and committing to a three-fold process of discipleship: dying to self, living by faith, and knowing the heart of Jesus. -------------------------------------------------------------------------------- The Context of Preparedness Physical vs. Spiritual Readiness The narrative begins with an analysis of human instincts regarding danger. Using the "honey badger" as a metaphor for unexpected threats, the source notes that people often engage in "guy code"—theoretical discussions on how to survive animal attacks or positioning themselves in restaurants to face the door. This instinctual preparation for physical danger stands in stark contrast to spiritual passivity. The source cites a tragedy in Kansas where a school bus driver failed to intervene during a fatal Rottweiler attack on a student, using it as a cautionary tale: many individuals do not know how they will react when "the rubber hits the road" spiritually. The Prison Cell Perspective The mandate for spiritual readiness is framed by the Apostle Paul's circumstances while writing 2 Timothy. Status: Paul was a political dissident, not a common criminal. Environment: Writing from a prison cell with minimal light, likely using charcoal and scraps. Stakes: Paul was facing imminent execution (beheading), a "privilege" reserved for Roman citizens. Despite these "monsters," Paul's instruction to Timothy remained: "Preach the word; be prepared in season and out of season." -------------------------------------------------------------------------------- The Subversive Power of the Euangelion The document provides a historical and linguistic analysis of the term "Good News" (Greek: euangelion). Imperial Context: In 8 BC, an inscription regarding Caesar Augustus used euangelion to announce the birth of a "savior of the world" and a god. Christian Subversion: When early Christians used the term to describe Jesus, they were making a direct political challenge to Roman authority. The Meaning of "Christ": The title "Christ" literally means "King." By proclaiming the euangelion of Jesus the Christ, Paul was announcing a new King whose kingdom was based on the "rule and reign in the hearts of humans" rather than geography. -------------------------------------------------------------------------------- The Mandate for Readiness: "In and Out of Season" Using the analogy of basketball in Kentucky—where the "season" is effectively year-round—the source argues that spiritual readiness must be constant. The Methodology of the Body Paul's instructions for spiritual engagement include three specific actions: Correct: Providing necessary adjustment to others. Rebuke: Offering firm warnings when needed. Encourage: Providing deep support and motivation. These actions must be delivered with "great patience and careful instruction." The "Hot Potato" Phenomenon The source identifies a common failure in spiritual readiness termed "hot potato." In this scenario, God "passes the ball" (an opportunity to share faith or provide support) to a believer, but the believer immediately passes it away out of fear or lack of preparation instead of "shooting" (taking the opportunity). -------------------------------------------------------------------------------- The Individual as God's "Rescue Plan" A primary theme of the document is the decentralization of ministry. The source asserts that the individual believer—not the pastor—is God's rescue plan for their specific sphere of influence. The Limitations of the Clergy: Pastors are not present in secular workplaces (e.g., a Toyota factory floor), in private meetings, or in classrooms where people are experiencing crises like divorce or abuse. The Great Commission: In Matthew 28:18-20, the "imperative" is to make disciples. This is achieved through three supporting actions: going, baptizing, and teaching. -------------------------------------------------------------------------------- Framework for Spiritual Preparation To move from passivity to readiness, the source outlines three essential disciplines: DisciplineDescriptionBiblical ReferenceFind Your PurposeRecognizing oneself as God's "handiwork" created for specific "good works."Ephesians 2:10Find Your PeopleTransitioning from "rows" (passive church attendance) to "circles" (community groups) for accountability and correction.Hebrews 10Grow as a DiscipleEngaging in the three-fold process of spiritual maturity (see below).N/A The Three Pillars of Discipleship Die to Self: This involves "crucifying" sin. The source argues that people struggle with sin because they "like it" and treat it as a "little savior" for a temporary fix. Dying to self means admitting this attraction and choosing to end it. Live by Faith: This is defined as a practical shift in internal dialogue. Instead of self-talk regarding worries, the believer adds "God" or "Jesus" to their thoughts, turning inner dialogue into a constant prayer life. Learn the Heart of Jesus: Head knowledge of the Bible can lead to "Phariseeism." True discipleship requires knowing Jesus' heart—specifically his sacrifice. -------------------------------------------------------------------------------- Conclusion: The Reality of the Sacrifice The document concludes by emphasizing the visceral reality of the Crucifixion to illustrate why knowing the "heart of Jesus" is paramount. Jesus' death is described as a transition from complete purity to becoming "all of the world's sin all at once," experiencing the weight of every human atrocity. The ultimate goal of spiritual preparation is not to become a biblical scholar but to be "dumb enough to shoot"—to act on faith when the opportunity arises, regardless of formal training or perceived status. The source illustrates this with a personal anecdote of a 17-year-old on a BMX bike leading a friend to baptism, proving that the power of the "rescue plan" depends on God's authority, not the believer's expertise.
In this episode, we dive into the reliability of the two biggest Amazon SaaS tools - Helium 10 and Jungle Scout. We explore how close these tools come to actual Amazon data and discuss what sellers should keep in mind when using these tools for product research and estimating sales. Timestamps 00:00 - Amazon keyword and sales data tools 00:57 - Why its hard to rely on brand analytics alone 1:21 - How data was collected from three different brands and categories 2:19 - Methodology for comparing keyword search volume 4:42 - Keyword volume discrepancies 5:56 - Overall variance: Jungle Scout vs. Helium 10 accuracy 6:08 - Verifying Helium 10 data and common data interpretation issues 7:03 - Limitations of Helium 10's dashboard and metrics interpretation 8:03 - Possible reasons for Helium 10's inaccuracies 9:00 - Brand analytics data vs. third-party tools 12:21 - Amazon's own sales estimates and their reliability 13:15 - Price comparison: Helium 10 vs. Jungle Scout 14:13 - Alternative affordable tools like Seller Sprite and their usefulness 15:11 - Final thoughts Resources Helium 10 Jungle Scout Seller Sprite Quiet Light Brokerage As always, if you have any questions or anything that you need help with, leave a comment down below if you're interested. Don't forget to leave us a review over on iTunes if you enjoy content like this. Happy selling and we'll talk to you soon!
In this episode, we explore the complexities behind Ethereum's gas pricing, focusing on the proposal EIP 7904, which aims to adjust compute gas costs for a more efficient and secure network. Our guests, Yacek Glen and Maria, share insights from their research, the importance of benchmarking, and how these changes could shape Ethereum's future.
On this week's mailbag episode, JJ discusses the Jaylen Waddle trade, looks at AJ Brown's outlook, talks through some ZAP Model changes, and more. Make sure to check out LateRound.com to order the 2026 Late-Round Prospect Guide. Want to get dynasty rankings while accessing the amazing Late-Round community on Discord? Become a Late-Round member today.See omnystudio.com/listener for privacy information.
#375: Julie Nguyen grew up in Orange County, California. She studied economics at Stanford University, went on to work at JPMorgan, and then was one of the earliest employees at Lumosity, helping the business grow to nearly 200 employees and 60 million members worldwide.Growing up she struggled with bouts of asthma, eczema, and weight gain. Julie theorized that perhaps her diet was the true cause of many of her illnesses. Julie spent six years researching nutrition science, testing numerous diets, and working with nutritionists and personal trainers to get a better understanding of how food affected her body. In the process, she cured all of the health problems that she had suffered from for years.The experience led Julie to found Methodology, a premium food delivery service that uses only nutrient dense, whole foods. All ingredients are sustainable, local and organic. There's no refined sugar, gluten, dairy, canola oil, chemicals or preservatives.Years later, she also created and developed Maison Methodologie, a Parisian-style protein patisserie that uses easy-to-digest pre-industrial grains and also has 12-16g protein per cookie.What you will learn:How to balance out your masculine and feminine energy and knowing when to bring more of one side outWhy it's better to sacrifice salary in the early years of your career for long-term goalsThe reality behind building a successful business that lasts for 10+ yearsLearning how to tune out the noise and be more confident in who you are and what aligns for your life, even when it's different from society's beliefsHow traveling expands your worldview and why it's more beneficial to do it sooner than laterEnjoy 10% off your first order of Maison Methodologie with code WHATFULFILLSYOU at checkout: https://maisonmethodologie.com/BILT Credit Card Info (Pay Rent and Earn Points):https://bilt.page/r/HQ06-ZV7OReceive weekly personal insights from Emily's email newsletter and subscribe hereWatch Full Episodes on YouTube: https://www.youtube.com/@whatfulfillsyou/videosENJOY 10% OFF THE WHAT FULFILLS YOU? CARD GAME AT www.whatfulfillsyou.com - code "WHATFULFILLSYOU10"Follow the What Fulfills You? Podcast Instagram: https://www.instagram.com/whatfulfillsyouFollow Emily Elizabeth's Instagram: https://www.instagram.com/emilyeduong/Read more on Substack: https://whatfulfillsyou.substack.com/Support this podcast at — https://redcircle.com/what-fulfills-you-podcast/exclusive-contentAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy
Claude Cowork came out of an accident.Felix and the Anthropic team noticed something interesting with Claude Code: many users were using it primarily for all kinds of messy knowledge work instead of coding. Even technical builders would use it for lots of non-technical work.Even more shocking, Claude cowork wrote itself. With a team of humans simply orchestrating multiple claude code instances, the tool was ready after a brief week and a half.This isn't Felix's first rodeo with impactful and playful desktop apps. He's helped ship the Slack desktop app and is a core maintainer of Electron the open-source software framework used for building cross-platform desktop applications, even putting Windows 95 into an Electron app that runs on macOS, Windows, and Linux.In this episode, Felix joins us to unpack why execution has suddenly become cheap enough that teams can “just build all the candidates” and why the real frontier in AI products is no longer better chat, but trusted task execution.He also shares why Anthropic is betting on local-first agent workflows, why skills may matter more than most people realize, and how the hardest questions ahead are about autonomy, safety, portability, and the changing shape of knowledge work itself.We discuss* Felix's path: Slack desktop app, Electron, Windows 95 in JavaScript, and now building Claude Cowork at Anthropic* What Claude Cowork actually is: a more user-friendly, VM-based version of Claude Code designed to bring agentic workflows to non-terminal-native users* Why “user-friendly” does not mean “less powerful”: Cowork as a superset product, much like how VS Code initially looked simpler than Visual Studio but became more hackable and extensible* Anthropic's prototype-first culture: why Cowork was built in 10 days using many pre-existing internal pieces, and how internal prototypes shaped the final product* Why execution is getting cheap: the shift from long memos, specs, and debate toward rapidly building multiple candidates and choosing based on reality instead of theory* The local debate: why Felix thinks Silicon Valley is undervaluing the local computer, and why putting Claude “where you work” is often more powerful* Why Claude gets its own computer: the VM as both a safety boundary and a capability unlock, letting Claude install tools, run scripts, and work more independently without constant approval* Safety through sandboxing: why “approve every command” is not a real long-term UX, and how virtual machines create a middle ground between uselessly safe and dangerously autonomous* How Cowork differs from Claude Code: coding evals vs. knowledge-work evals, different system-prompt tradeoffs, longer planning horizons, and heavier use of planning and clarification tools* Why skills matter: simple markdown-based instructions as a lightweight abstraction layer for reusable workflows, personalized automation, and portable agent behavior* Skills vs. MCPs: why Felix is increasingly interested in file-based, text-native interfaces that tell the model what to do, rather than forcing everything through rigid tool schemas* The portability problem: why personal skills should move across agent products, and the unresolved tension between public reusable workflows and private user-specific context* Real use cases already happening today: uploading videos, organizing files, handling taxes, managing calendars, debugging internal crashes, analyzing finances, and automating repetitive browser workflows* Why AI products should work with your existing stack: Anthropic's bias toward integrating with Chrome, Office, and existing workflows instead of rebuilding every app from scratch* Computer use one year later: how much better it has gotten, why vision plus browser context is such a superpower, and why letting Claude see the thing it is working on changes everything* Why many “AI verticals” may get compressed: specialized wrappers may matter in the short term, but better general models and stronger primitives could absorb a lot of narrow use cases* The future of junior work: Felix's concerns about entry-level roles, labor-market disruption, and whether AI can compress early-career learning into denser simulated experience* Why Waterloo grads stand out: internships, shipping experience, and learning how real teams build products versus purely theoretical academic preparation* The agentic future of the desktop: what it means for Claude to have its own computer, whether AI should act on your machine or a remote one, and how intimacy with personal data changes the product design space* Why Electron still mattered: shipping Chromium as a controlled rendering stack, the limits of OS-native webviews, and why browser engines remain one of the great software abstractions* Anthropic's Labs mentality: wild internal experiments, half-broken future-looking prototypes, and the broader effort to move users from asking questions to delegating increasingly long and valuable tasks* Why the endgame is not just more capability, but more independence: teaching users to trust AI with bigger scopes of work, for longer durations, with fewer interventionsFelix Rieseberg* X: https://x.com/felixrieseberg* LinkedIn: https://www.linkedin.com/in/felixrieseberg* Website: https://felixrieseberg.com/Anthropic* Website: http://anthropic.comFull Video PodTimestamps00:00 — Cheap execution and building all the candidates00:44 — Intro in the new Kernel studio02:47 — What Claude Cowork is04:18 — Why user-friendly can be more powerful05:33 — How Anthropic built Cowork07:09 — Prototype-first product development08:00 — Why local computers still matter09:20 — Skills, primitives, and platform leverage12:13 — Cowork's architecture: VM + Chrome + system prompt15:38 — Felix's own bug-fixing Cowork workflows17:38 — Local-first agents20:16 — Evals, planning, and knowledge-work optimization23:14 — What Anthropic means by evals24:21 — Scaffolding, tools, and why skills matter27:44 — Demo: YouTube uploads and self-generated skills31:03 — Calendar automation and cleaning your desktop34:47 — Browser context and why DOM access matters37:47 — Skills portability and plugins44:36 — Which AI categories survive?46:19 — Junior jobs, simulated work, and labor disruption52:00 — Gradual takeoff vs big-bang takeoff53:42 — Finance, taxes, and enterprise verticals56:24 — Vision and the improvement in computer use57:31 — Why Claude writes its own scripts58:06 — Should Claude have its own computer?1:01:26 — Windows 95 in JavaScript1:03:19 — VM tradeoffs and sandbox design1:07:23 — Approval fatigue and safe delegation1:11:18 — The future of Cowork1:12:27 — What comes next for agentic knowledge work1:15:13 — Electron, Chromium, and desktop software lessons1:22:16 — Multiplayer agents and coworker-to-coworker workflows1:26:05 — Anthropic Labs and closing thoughtsTranscriptAlessio: Hey everyone. Welcome to the Latent Space Podcast, our first one in the new studio. This is Alessio, founder of Kernel Labs, and I'm joined by swyx, editor of Latent Space.swyx: Yeah, so nice to be here. Thanks to, uh, TJ, Alessio, Allen helping to set everything up. It looks beautiful. We even have the logo outside.Yeah, kind.Felix: It's like really nice, right? When you walk in here as a guest, you're like, ah, this is a serious production. You're like, feel it immediately.swyx: Yeah. Felix, you've been, you're, you're currently a product manager of Cowork or,Felix: uh, really Technicswyx: Eng. Yeah. The, the identities are kind of vague member technical staff.Felix: I know member staff is like, the official title will carry around forever.swyx: Yeah. I basically kind of wanted, like we've been. Kinda obsessed. I, I've been using it a lot, even for managing latent space. Like, uh, cowork helps me upload videos and like title things and like edit and everything. It's, it's like really amazing.Alessio: Cool. He said multiple times Cowork has said gi in the group track.swyx: Yeah, yeah, yeah. So, so we have a second, uh, we have a second channel, uh, for latent space tv. Uh, and I, uh, and uh, we basically, this is our Discord meetup. Um, and I I, we have like Claude Coworks, it might be a GI, I don't know if we, we have, uh, uploaded it yet, but one of the sessions was like a, like a Claude cowork thing.Felix: I, you have to see, I would love to see it. Like, I'm so curious, like one of the most fun parts of my job is like constantly see the weird things people use Cowork for because it's obviously like very hard for us to actually design for specific use cases we do. But like every single person who's like most amazed is usually amazed about a thing that I didn't even expect cowork would be good at.Um, we have a new designer and it's one of the first small tasks. I was like, Hey, we need like a new emoji for cowork for our internal stock. It's like a pretty small thing. I like, can you please do it? And he drew an SVG and just gave it to coworker was like, can you animate this emoji? And now it has like this beautiful loopy animation.Um, and I mean, I think obviously this goes down to like, it turns out you can do more things with code than you expected, but it, it's like that kind of stuff that is really fun to me. So, long story short, I would love to see like, the kind of things you're doing.swyx: I'll pull it up. I'll pull it up.Felix: Yeah. Yeah.swyx: Uh, but before we get into it, I, I think always wanna start with like a top level. What is Claude Cowork for people who haven't heard of it? Haven't tried it out.Felix: Okay. Uh, real quick, Claude Cowork is a user friendly version of Claude Code. So the way it basically works is we have Claude Code and for us, fairly impressive agent harness that over December we noticed more and more people are using either, even though they're not technical, they, they're not at home in the terminal or they are at home in the terminal, but they started using Claude Code for non-coding workloads, right?Like managing expenses or like filling out receipts or organizing a knowledge base. Like there was a big obsidian moment that a lot of people liked and we wanted to capitalize on that, but also bring, bring this capability to people who are not terminal native and who might not know how to like brew and store something.So cowork is Claude Code running in original machine with a little bit of padding, a little bit more guardrails, making it a little safer and a little bit more convenient for people who don't wanna first open up the terminal when they go to work.swyx: It's interesting, uh, that is kind of. Pitch that way as a more user friendly thing because I always feel like it, it, to me, I I treat it as like why I'm familiar with Claude Code.Like we, we did a Claude Code episode Yeah. A year ago. But this one is like even more power user tools ‘cause it, uh, it kind of integrates much better with like clotting Chrome and, uh, in all the, all the other tooling. But like, maybe, maybe that's like a perception thing, right? LikeFelix: No, honestly, I don't think you're wrong.This is like a, a thing I've been thinking a lot about for like the last two weeks. So,swyx: but when they say user friendly, it's like, oh, it's the dumb down version. But no, actually this is the superset.Felix: Yeah. Like, I think a similar thing happened, A similar thing happened to me about 10 years ago, like maybe 12 years ago when I was at Microsoft and we started working on, on Electron and like browser-based technologies and cross-platform stuff.And one of the first use cases was Visual Studio Code, which used to be a website. And the initial narrative was, or Visual Studio Code is, is like a more user-friendly version of Visual Studio. But in a similar vein, I think there was some voices saying, oh, this is. For serious developers, like, we're not gonna use this.Right? For like anything. And I think in the end what happened is people have different stories about why Visual Studio Code became such a big thing. But my personal, my personal belief is that the Hackability and the extendability has like played a pretty big role, right? You can hook in Visual Studio Code that like almost any workload, it's so easy to hack on, so easy to put extensions for it.And I think cowork might be hitting a similar thing where it's very easy to extend and it's very easy to bring into your workflows. Uh, so the convenience I think is a bit of a, it's obviously the thing we strive for as developers, but I think the way people find value in it then is by probably mapping it onto whatever they actually have to do in their job.Alessio: So end of last year, you see the spike of like non-technical usage and clock code. What's the design process to say we should make clock code work? Because I mean, you built it in only 10 days. Um, I'm sure there was some discussion before on whether it's easier to use mean. You know, like making, making like a desktop GUI is obviously one way to do it, but like there's a lot of nuance in the product.Like maybe talk people through what was like the trigger of like, we should build a separate thing. We should not build like a different plot code thing. And then maybe some of the more interesting design decisions that maybe you didn't take.Felix: Yeah, I think philanthropic, we've been thinking about ways to move people who are comfortable with using Claude to answer questions and bring more of the power of like this thing to now like, execute tasks for you.I can like solve problems for you can like build things for you. How do we bring that capability to people who are currently mostly comfortable with like a like question answer paradigm within the chat. And we've had a lot of prototypes around that. Just going back as far as like easily a year and a half.Like we had a lot of people working on that. Um, and internally philanthropic is a very prototype demo, first culture. We have a lot of like internal prototypes that don't reach the public. What Cowork actually became is like we sort of picked the right pieces out of the many prototypes that we had.Right. And that's, that's maybe also like, I think an important qualifier whenever people mention this like 10 day number. I do think it's important to me to mention that within Double Scratch there was like a lot of stuff already happening, right? Like, and I think it's important for people to remember that when you build a website, you use React, you use like a bunch of other things.And this is like a similar scenario with like a lot of pieces we already had. Um, and in terms of decision path, I think we live in like an interesting new world where execution is actually quite cheap.swyx: Mm-hmm.Felix: So maybe, maybe what you would do That's so crazy. The year. I know it's wild.swyx: You should be, ideas are cheap.Execution is the hard part. IFelix: know. And like the, we, we used to live in this world maybe where you would take a product manager and the product manager would go to a number of potential customers and in this like very low bandwidth way, would try to. Try to like tease out what are the problems they're having, what are they willing to buy?Um, and then maybe what can you build to like drive out that need and then you go back and you like draft a spec and you think about it and then like you make a design and you execute it. We internally philanthropic app, not pretty much closer to the point where we're like, don't even write a memo, just like build, like let's build all the candidates very quickly.Let's just build all of them and then pick the best ones. I think the, the decision that is most impactful both for the product as well for the users right now is like the way we put value on your local computer. I think that's a big decision point a lot of people have thought about. Should this thing, whatever it is, should it ultimately run into computer or should it run in the cloud?‘cause they're big trade offs, right?Alessio: I guess like if we solve auth, it would be easy to do in the cloud. But I think like the fact that I can just download any file from anywhere and then put it and cowork there, it's like a big unlock. Um, I mean it's interesting you mentioned reusing certain pieces. I think this is something I've been thinking about even with Claude Code, right?The price of like writing code is going to zero, blah, blah, blah. But it actually seems like the value of having some sort of platform substrate is like increasing because as you build these new things, you can kind of plug them together.Felix: Yeah.Alessio: So I almost feel like when people are saying, oh, the value of a lot of software is gonna zero because you can recreate it, to me it's almost like the opposite.It's like having an existing platform to build on top of. It's like even more valuable because you can kind of bolt things on.Felix: Yeah.Alessio: You have obviously mcps, you have skills, you have like obviously the models, which is a big part. All these things kind of come together. Do you feel like that's a valid way to think about it, where people should invest even more in kind of like primitives.To rebuild on or are you like recreating a lot of it each time because like things change and it's easier to rewrite than reuse?Felix: You know, I think, I think you're right. I think you're right that the holistic platform is really useful. And this is maybe a whole like a somewhat contrarian view to a lot of people in ai.I actually don't think that the future is going to be hyper personalized software down to the point where everyone is running their own version. Like, I actually think it's going to be quite hard for all of us to have our own internal chat tool and like, if I wanna talk to you, likeswyx: howFelix: is that gonna work, right?In the, in the context of cowork and how we build it, I think it's a bit of a combination. Like what the, the execution that gets cheap is not necessarily rebuilding all the primitives. I think our priori, there's also not a lot of value in it. So for instance, my team did not think about rebuilding clock code.We're like very much started with the. The core thesis of this should be Claude Code.Mm-hmm.Felix: And then we'll like build things on top of it. The part of the execution that gets a little cheaper is like, how do you take all of these Lego pieces and put them together in a way that makes sense for users?It's like actually valuable. You have so many different approaches now in terms of what kind of, what kind of things do you actually elevate to a primitive, do you strongly believe that all your products should be built by just combining primitive that the public also has available? Do you keep some things internal?Um, and I think that's still evolving, but I think what's probably gonna go away is like, I'm not sure if it's gonna fully go away, but I'm gonna say, I think for me personally, I will probably no longer try to come up with a really good product without testing up with people. This is not a new concept, but wherever you used to have to make costly decisions around, do we pick technology A or technology B, or do we like, um, build it this way, build it the other way.I really strongly believe now you just build all of them and try them out with a small focus group and then whatever, whatever is better is what you go with. Right. And that, that is probably quite different even from how we maybe worked a year ago. Right. Like, I think, I think this happened very recently.Alessio: Yeah. I started building something in on Electron since you're here. Coincidence. Uh, but then Electron and like SQL Light are like, there's like some issues that like between development and like, uh, building anyway. And I was like, let's just rebuild the whole thing in Swift and just recreated the whole thing in Swift.And it's like, I. It's done.swyx: You know, I didn't take any effort. I, I, I don't even know Swift.Alessio: Yeah, exactly. I was like, I'm the, I'm not reviewing it anyway, whatever. You can write in whatever language you pick, but the important stuff that I did was not write the electron bindings. Yeah. It was like the logic of what happens in the app, you know, and then the model is like, yeah, I can just recreate the same thing as withswyx: Yeah.I, I think you still want, especially for people who are doing like high performance software or like very complex software, uh, you still want like, some view of the architecture. Uh, but you can use markdown for that,Felix: right? Yeah.swyx: Uh, you don't actually have to read the code again. I, I'm still like on a sort of like a definitional thing.Um, can we build a good mental model of Claude Cowork? Um, this is what I have, right? Like you you said it's like fundamentally cloud co. We don't wanna touch it. There's the cloud app, there's clouding Chrome. I think you guys do something different in planning, but, uh, I've been talking with Tariq who is on the cloud co team, and you guys are, he's like, no, we just exposed planning.Maybe we can clarify like, what are the major pieces. That people should be aware. It goes into cowork, like,Felix: okay, I think you basically have them. So really, um, you can, you can take planning more or less out. I think there's a few things that are really valuable in cowork. Um, the virtual machine is probably the most powerful thing.So we currently run like a, we currently run like a lightweight VM and we put clocked out into the vm and we do that for, for, um, a number of reasons. Safety and security is a big one, but even if you, even if you ignore for a second safety and security and you're just like, okay, Yolo, I want this thing to do whatever.It is quite powerful to give Claus on computer that is like generally a good idea. And in terms of architecture and UX and everything else that we've been working on, philanthropic, it often is quite useful for you to like anthropomorphize, um, clot aggressively and just be like, this is a person. What will you do if you give a, if you had a person, right?Yeah. And the analogy I've given my dad this morning who is still like quite insistent on using chat even for like coding things, is if you were a developer and your employer told you that you don't need a computer, they're just gonna like, send you emails with a code and you send emails with code back like that, maybe work for Patrick Miles in the back, but that it's not very effective.Um, so what we can do with the VM is because it's a, it's a Linux system, Claude Code has more or less free reign to install whatever needs to install. It can install Python, it can install no js. We do have strict network ingress and egress controls. So you can still, as, as a user in like plain human language, make it clear to, to the entire system what you're okay with and what you're not okay with.But at no point do we have to ask a real person, like a, like a person who might be in marketing or a lawyer. I'd have to go to a lawyer and be like, are you okay with me installing Homebrew?Alessio: Yeah, yeah.Felix: Right. Because the implications of the question and the answer are complex and nuanced and like, not, not easy to reason about.This gives us a lot of distraction that makes Cloud very powerful. Now then around it, we, we do probably have a number of things that also keeps growing almost every single week that you're probably noticing that make cowork maybe better for certain tasks than just cloud. Cloud on its own. Yeah. But most of those actually live in the system prompt.They're about like, what can we infer about the work that you do? What can we, what can we intru in the system prompt to make that more effective? It's of course the like very tight integration with Cloud and Chrome. You're noticing that a lot of people, especially as the models get better, a lot of people throw up their hands when it comes to MCP connectors in this area.I'm not gonna, I'm not gonna go through like 25 M CCP connectors, click off everywhere and then like half of them don't let me do the things anyway. So Cloud and Chrome is quite powerful because we can just talk to the cloud and Chrome sub agent and that will just do things for you.swyx: Yeah, so, so one example right in MCPI, honestly, I think that the state of MCP is kind of, kind of.Really hard to integrate. Um, I need to, I needed to add, uh, Figma MCP to the coding agent that I use.Felix: Yeah.swyx: Uh, and, but I didn't wanna read the docs, so I just had caught to it. And it's, it's great at reading docs and the same, same way I had to set up like a Google Cloud, um, account for some project I was working on and get some API keys somewhere.And Google Cloud is famously super hard to navigate, so I just didn't wanna deal with any of it. I just used Claude CoworkFelix: within the first week of developing on Core. This happened very, very quickly. Um, I caught myself by starting to use cowork for coding tasks, which is not ostensibly what we built it for, right?We don't need to. But I found myself, um, I found myself like on our internal, internal tool that we have for, to collect crashes and just like debugging information and I found myself sort like picking out the ones that I think we can easily fix versus the ones that might be like kernel corruption or something else on the operating system.And I found myself sort of picking these out and then just telling Clark, go fix this bug. I was like, what am I doing here? Go one level up, tell a cowork, I want you to go to all these crash tools. I want you to find all the bugs that you think are fixable and not like an operating system crash. And then I want you to tell another cloud to like fix all of that.Um, and that's, that's, that's sort of another cloud,swyx: just so it can spin up another instance or,Felix: uh, it, currently what I do is, um, and this is a bit of a hack, but I tell it to use clockwork remote to which website itself? Yeah, that's interesting. So you basically take, if you, if you imagine like a dashboard with like 20 bucks, you, this is remote control or clock or remote, or, sorry, I just wanted to confirm what, the way I'm using it is.I have cowork running and I'm telling cowork, here's where I normally go every morning to find the latest bugs. Go read the entire bug list, separate out which ones are fixable, which ones are, are fixable, and then for the fixable ones, four is this almost loop. For each bug, write a markdown file with a prompt.And then for each markdown v, that is a prompt. Start of a cloud set. So natively Claude Code hasswyx: this concept of subagents. Mm-hmm. And this is basically a subagent, but you're not using the subagent functionality.Felix: I'm not using the subagent functionality. And the reason I'm not is because I'm firing that off as a Claude Code remoteswyx: task.Felix: Yes. That's kind of nice. ‘cause then I can just fire it off. I can go to my next meeting and in Claude Code remote. Now the work is happening.swyx: Mm-hmm. Yeah. You, you see like you're already starting to use the cloud over your local machine. And I think this is one of those things where like. Shouldn't just everything just be cloud first, right?Felix: Ah, this is such a good group. I'm like solely bad about this. I have so many thoughts about that. Okay. So I generally believe that Silicon Valley overall is undervaluing the local computer. And my default argument for that is always how come we're all using MacBooks and not like an iPad or a Chromebook?Um, that there is like still value in, in having a local machine. And now when I think about Clot, it's this entity that is supposed to be very useful to you, like it tremendously useful to you. I think that entity needs to have access to all the same tools you have access to. Otherwise it's gonna be hamstrung in like all these complex ways.And there's, there's sort of two approaches we could take. We could say, okay, we're gonna like one by one chip away at everything that is at your computer and move it into the cloud. That's, that's one way to do it. Um, and I think other products have taken that path. I personally, this is a very personal opinion, but I personally, for the amount of tools that I use.Just don't have the patience to give another tool like permissions to every single thing and keep those permissions up to date. The second thing that I'm still grappling with, and I don't have a good answer for anyone just yet, but the second thing I'm still grappling with is what does it look like for someone to slurp up your entire work and put that in the cloud?Like if I, just as an example, like if you could click a button and it just clone your entire computer into the cloud, is that something that you would want? I'm not totally convinced yet that all everyone will. Mm-hmm. And that is sort of like upstream of all the technical issues we're gonna have. ‘cause like in general, I think the world is not ready for this kind of stuff.Like, I'll give you one quick example that would probably be very easy for us. So as a desktop app, we in theory with your permission, can do a lot of things on your computer, including reading your Chrome cookies. If we really want to do right, we could take your Chrome cookies, you would have to decrypt them for us.We could put those on the cloud if we really felt like it. Pretty easy solution. That would be super cool. We could just be like, oh, we can do all your tasks in the cloud now. Um, a lot of websites, thanks, include it. If, if they see the same authentication from like two different locations, we'll just lock down your account and now you have to go to the branch and be like, okay, I, I'm here with my passport.You actually know that. Wow. Yeah. As tired as well are of the term agent for the age agent future, I think there's a lot of stuff that sort of slowly needs to catch up and until that's the case, the way I, as someone's working on clock and make Cloud most effective is to like put it where you are working.swyx: Anything else? I thought with our mental model, so like, basically like, uh, part of me also just want, like the more I understand how it works, the more I can use it to its full potential. Right?Felix: Yeah.swyx: And so what I'm get hearing from you is you told me to delete the planning thing. You're not doing anything special on, on the, that's only exclusive to Qua cowork.Felix: We have some tricks for this sort of like change week over week. We eval cowork maybe against different use cases than he would evil clock code, right? If you think about it this way. Okay, so like clock code is our eval clock cowork. Yeah. So clock code is like quite optimized for coding tasks and we mostly value it whether or not we're getting better or worse depending on how good it is at like a typical suite job.And Clark Cowork on the other hand, we evaluate more against typical knowledge work, the kind of stuff he would find in finance or in like maybe a, like in like a legal office. Um, my personal use case is always like managing my things, like managing my personal mortgage or something like that, right? Or like wealth planning for me and my family.Those are the kinds of use cases we eval, clock cowork on. And what you might be picking up on is like the subtle changes we make to the system. Prompt what we put in the system, prompt how we steer, clot with the tools we give it. Um, like either it'd be better in one or the other direction and whether there's a trade off, try us exist a lot.CLO code will be better of a code and Claude Cowork will be better. For non-coding tasks, will those gaps still exist in the next three generations of models? It's like a little unclear to me though.swyx: Yeah,Felix: because right now these like hyper optimizations we make, I'm not sure for how long they're still be relevant.swyx: I think what I was referring to was also, it, it just, uh, it qualitatively felt different when I probably, it's just all prompting and I'm reading too much into it, but like the, the fact that it comes out with like a nine step plan, I can edit the plan and give feedback and, and, and see it execute the plan.Yeah. It felt more long range than in Claude Code, but maybe that already existed in Claude Code and you just build a nicer UI for it.Felix: It's kind of both. Um, like if the Clark Code people who build the planning functionalities would city, they probably say yes, we have all of those things in Clark code and they do.Um, I think people tend to give cowork. Tasks that are maybe of longer time horizon, I thought isswyx: so long. Yeah.Felix: That's like one thing, right? It's just like that the, the chunk of work tends to be maybe a little bigger. And then the second thing is that because the work, when it gets longer, it gets a little bit more ambiguous.We do tell co-work to make heavy use of the planning tool or to make heavy use of the ask user question tool, right? We do want it to come up with like. Different scenarios of, okay, tease out what the user actually wants. Don't go off to work for like four hours and then come back with the wrong thing.And you're probably picking up on that.swyx: Yeah.Felix: Um, I wish I could tell you I like built this magical thing and it's like, there's some secret sauce,swyx: but No, no, no. I mean, it's, it's just clarity is good that, you know, engineers just want to know. Yeah. They can, they can plan around it. And then I think also for me, um, I am realizing I have to switch to my, my other machine because this is a new machine that doesn't have my session.But, uh, yeah, the, the, the planning is really important for, for me to like approve or like to see whether it's like, it's right. The ask is, the question is so beautifully presented. I mean, it also, it also available in like cursor and, and in Claude Code. But like, I, I think like it's so nice to see that it, like it's kind of for me like to understand that it gets me, it gets what I want to do.Felix: Yeah.swyx: Yeah.Felix: It probably very hardswyx: just on the topical evals. Mm-hmm. When you say eval, I think people are very vague about what it means. Is it just like vibe testing or do you have like automated programmatic evals of Claude Cowork?Felix: When we say eval, uh, what we really mean is that we essentially take the entire transcript, including all the tools that clot has available ultimately to it, and we then measure what are the outputs, depending on what we tweak, right?So we do run that a lot. We use that in training. Um, we use that in, in like, if you sort of separate out post training from like the scaffolding around it. Cowork sort of exists in the scaffolding space, but obviously we also train on it a little bit. Um, so when we say eval, we mean given the certain transcript, what do the outputs look like?Including the file outputs as well as like the actual token outputs, like the ones that you see in the chat window.Alessio: I'm curious, um, how much of the failure modes are the model intelligence versus like the usage of the end tool to put the intelligence in? Like the well planning is like a good example, right?It's like one thing is to come up with a plan. The other thing is like make a nice spreadsheet. Yeah. That kind of runs you through the plan. Like how have you seen that? Well,Felix: the thing that I grapple with a lot is that whatever scaffolding you come up with, I think we still have a bit of sort of like model overhang where the model is dramatically more capable than right.Users end up using it for. And I think part of that is that we're just not getting the model all the tools to do all the things that's theory capable of, right? There's like one thing, um, however, whenever you do build the scaffolding, I'm sort of wondering at what point, at what point will that scaffolding go away and like how much you invest in figuring out what the right scaffolding is.It's kind of up to, it's a little bit of a bet. And one thing that I as an NJ quite enjoy is that like working in philanthropic and working at a frontier lab, I maybe have a little bit more insight into what's coming, coming down the chute in terms of like, what's the next model, what is the model capable of?What is good at, what is it bad at? And I'm, I'm increasingly wondering, is the right thing for us to like really invest too much in sort of these like scaffolding corrections where the model might otherwise not misbehave, but just not do the thing that you want?Alessio: Yeah.Felix: Or is it to just like give it as many capabilities as possible, try to make those safe so there's the worst case scenarios, likeno status might be otherwise.And then just simply wait a second for the next model drop. I'm personally, currently more leaning into the ladder. I think we're gonna see a lot of like applications and companies that do very impressive things with ai that in the short term might seem very effective ‘cause they're very specialized to individual use cases.But I think once models get better generalization and get better at like those specific use cases without being super guided on those, I'm not sure how long that's gonna stick around. And you can kind of, kind of already see this in like skills and NCP servers, right? Mm-hmm. We've, we've already seen sort of this like slow shift from MCP service to skills.And like, maybe a good example is Barry who made skills. He was initially hacking on something that honestly looked a lot, looked, looked a lot like what Cowork does today. It was sort of thinking about what if cowork, but for like people who don't wanna build code. Mm-hmm. And, um, he too did that as a prototype inside the desktop app.One of the first use cases we thought of were, okay, what, what are like coding like use cases that could really benefit from graphical interfaces and like from being a little separated from the actual underlying code. And everyone comes with the same answers. Data analysis,Alessio: right?Felix: Yeah. Or saying how many users do we have today?How many, like, it's always data analysis. And I think the thing that ultimately led to skills is that we wanted to connect this little prototype to our data warehouse and. The team very quickly discovered that like instead of building a custom tool for the thing to talk our data warehouse, they just like meet and embarked on follow like mm-hmm.Dear Claude, if you want to get data, here's the end point. Here's what the API looks like. You'll figure it out.swyx: Ah.Felix: And then it be hand over control. Yeah, yeah. Also just like maybe go one step up in the layer of abstractions, right. Just, yeah. Instead of, instead of telling the thing, here's ACL I, please call the CLI, or here's an MCP.Please call this ECT shape. Just like this is the end point. If you wanna know something, if you post here, maybe you can do post sql. It's gonna be okay. And that ended up being so effective that they started trying the same pattern of like just giving the model a markdown file that describes whatever it needs to do.That the whole thing eventually became skills and we're like. We should package this up. This is a good idea.swyx: Yeah. Um, we've had Barry Mahesh, uh, on, on our conference and uh, he's uh, definitely got a good idea there.Felix: Yeah.swyx: I wanted to show you the, how I've been using Claude Cowork.Felix: Uh, this is was my favorite part.swyx: This is this. So this is like me, uh, this is how we run the Discord. Uh, we literally, uh, at first I didn't trust Cloud Core. This was my very first usage.Felix: Okay.swyx: Right. So then I was like, okay, I will just try to manually download from Zoom all my recordings and upload it to YouTube. Yeah. Because this is a very laborious process.I got a click, click, click YouTube, um, isn't super user friendly. Uh, and it just did it. And then I was like, actually, you know, even the download from Zoom part, I should also. Put into Claude Cowork, and then I did it right. Here's a bunch of, and it starts compacting here, and it, and it, it starts to even be able to do things like look through the individual frames of the video to name the video so I can upload it auto automatically.Oh, that is, and this replaces my job as a YouTuber. We will forever appreciate your creative Yes. You know, and so that's great. Uh, but then by the way, it compacts and makes, makes like a new thing, right? So I, I don't, I don't have the initial, initial thing, but then I asked it to make its own skills so that it, so that something that's repetitive and one-off and human guided becomes more automated and I can use the skills independently and reuse them.Uh, and it obviously you can write skills and that goes into context and skills at the bottom here, which is, which is so nice. Um, so I have all these skills that, that I now sort of do on a weekly basis. Uh, I know you've released scheduled Coworks, which I haven't done yet, butFelix: course I should try them. I, I think this is like so wonderful and fun for me to see because.One thing that is very fun for me about skills in particular is that they're so easy to make. Like anyone can make a skill, like a text message, could be a skill, and they can be so hyper personalized to you. And this is like sort of the subtraction layer, right? Like, um, I, I'm just guessing, but I assume, heck, you are very good at your job.You're probably given this thing some guidance about how to do it, right? I,swyx: I just said, wrap everything up into, into a skill, right?Felix: Yeah.swyx: And then, uh, and then I was like, actually, sometimes I might need to break, uh, things apart because some parts fail or some parts might be needed in individually. So I told it to split one skill into three skills.So it's like a skill splitting thing, and then there's like a parent skill that just orchestrates all of them if I want to use that. You know, like, um, I think that's, that's like really good. Uh, and, and, uh, there's, there's one more part, which is the, uh, Google Chrome thing that I told you about.Felix: Yeah.swyx: Where I'm like, okay, you know, what's better than uploading, using Claude Coworks to YouTube?Like actually. Looking at the docs to like programmatically upload to YouTube and then putting that in a skill. And I've never done that before. I don't want to deal with Google Cloud. Yeah. So Claude Cowork does it for me.Felix: That is really cool.swyx: So, so I, I just, I don't care. I just, like, I do a thing. I don't, it doesn't really matter.Felix: That is really cool. And then you've, I assume paired the skill just with the script that it's built.swyx: Yeah, no, I just update, update the skills.Felix: Oh, that is beautiful. Yeah. That's wonderful.swyx: It's kind of like a skill, like, uh, uh, basically I think like the way that people ease into Claude Cowork is like take a knowledge work task that you would normally be clicking around for and then, uh, try to turn, turn that, and then you do the, okay, well what if you went further?Okay. And then when, if you went further, when, if you, and it sort of expand the scope of cowork as you gain trust with it and, and also teach it how to replace you.Felix: Yeah. It's like a little bit like playing factorial, but for your own life. Uh, like you say, you start really small.swyx: Yeah.Felix: You start automating something really tiny and like.Once it clicks, you keep adding onto this like automation empire. Just like make your life easier and easier. My favorite skill has been, um, every single morning Kohlberg starts looking at my calendar and make sure that there's conflicts because people tend to schedule a lot of meetings, sometimes last minute, sometimes miss it soft and painful.And a lot of products have existed like that A lot. I've written in the custom prompt there. I haven't made it a skill, um, honestly should.swyx: Yeah.Felix: But I've given it like pretty clear instructions about okay, here are some people, if they book over other meetings, I'm probably gonna go to their meeting. Like if Dario schedules a meeting.swyx: Right.Felix: Not try to reschedule down. Right. Um, and I think there's some other rules in there about like what kind of meetings I care more about what kind of meetings I care less about. What is okay to like, maybe pun like when I want to be, when I want to be working, when I don't want to be working. And it's those really small things that I can think kind of click with people.Right. When we launch co-work, I think one of the US races that went most viral on Twitter. X was clean up your desktop, which is stuff, because silly, that's such a smart thing, right? Like you don't need to model to clean up your desktop. Not really. Um,swyx: like this, like clean up my desktop.Felix: Yeah, exactly. Yeah.swyx: I need to, I need to choose my desktop, right? I guess give it access to my desktop.Felix: Yeah.swyx: Okay. Uh, okay. This is very scary. Oh, we'll do it.Alessio: I did, I did it with my downloads folder. It was like, you have so many term sheets and there's like eight copies of your rental lease for your office. I was like, all right.Like, don't yell at me.Felix: It's like, it's not such a small task. And then like, I, I would never go out there and normally otherwise and tell people I've pulled a product. It can organize your folder. Right. Um, because it feels small. But I think to your point like,swyx: oh, here's, here's the, here's the ask user questions.Felix: Yeah.swyx: Uh,Felix: beautiful. Right. Elite obvious junk. You probably shouldn't click that.Alessio: No.Felix: If he's not done right.swyx: As long as it's reversible, I don'tAlessio: make up blend to,swyx: yeah. Uh, yeah. No, I, I have a, I have a typical, everything is super messy folder. So, yes. I think this, this is super helpful. So this is a pretty simple task.Mm-hmm. But I've, okay, here it is. Right. Here's the progress. I don't see this in, that's why I'm like, this gotta be something different than, uh, than Claude Code, because I'm like, weFelix: do. Yeah. That's, we do system prompt that. We're like, all right. We want you to think about like, this task Yeah. Methodology.Yeah.swyx: And then I can, I can, I can do like little suggestions for, for, for these things. It's beautiful. Look at this. I, I can, I can like say like, oh, don't do that. Don't do this. It's amazing.Felix: I'm so happy. You like it. Um, I mean, the other way around, like we're part of the Clark core team, if you would like this in Clark COVID.swyx: Yeah. Yeah. Yeah. Uh, so, so yeah, I mean, uh, this is really good. Obviously I, I'm like kind of raving about it. Uh, you know, I have other things like sign up for pg e so if you can do phone calls for me, that'd be great. Um, I, I do, peopleFelix: have done that. Obviously you can't do that natively, but people have done that with like, various other providers.swyx: Yeah. Uh, and then this is like signing up for the Figma MCP. Um, I, I really am trying to do like everything, um, data analysis as well. I do think, um, oh, design to code, uh, very, very good. Right? So like, here's a Figma file, take it. And then this is where like a lot of other tasks is like knowledge work, like replace my manual clicking, but this is no, I would normally use Claude Code or uh, Claude Code for this, but because I perceive that you have better Chrome integrationFelix: mm-hmm.swyx: I, I think you can actually do a better job of this. And I, this, this is one shot at my, uh, conference website.Felix: That's pretty cool. Like at some point I would love to like, hear how you feel about code. In the desktop apps, which is like I never use, which is the, the same team. Same team.swyx: So I use the call code in terminal, which I, I perceive to be the default way of cloud coding.Felix: So one thing this has,swyx: sorry, I'm just like, I'm notFelix: here, I'm not here. All products. Can I talk about other stuff? Like I, I'm not sure if people out there wanna like hear me advertise my stuff for like an hour. Please do that. Um, this thing is like a builtin browser, which is a thing a lot of products have said.Yeah, it's a builtin browser. And I think giving cloud eyes into like what you're actually working on makes it so much more effective. And that's probably what you've seen in cohort because it can see Chrome, it can like debug the dom, it can like see things. Um, that does make it more powerful.swyx: Yeah. So, so I think, uh, my mental model was kind broken.‘cause I only use this cowork because I thought it had a, a browser thing in it. But I understand that the Claude Code app. The app version of Claude Code does have a built-in browser. I've seen, I've seen this preview thing.Felix: Yeah.swyx: I just, I've never used it.Felix: But in the end, in the end, you sort of have it by hard.Yeah. You basically get the same thing. Right? Like the, the, the additional skill that you're describing is chart is better if we can see what it's working on. Right. That's, that's sort of like the summary here and like whether it's using your Chromeswyx: Yeah.Felix: Or it's just like making up its own little like browser.It doesn't really make a big difference because either way it's gonna see what it's working on and that just makes it much better. And then you don't have to run QA for your cloud.swyx: Why doesn't it pick up my existing Claude Code sessions? ‘cause I, I mean, obviously I've used Claude Code, but Excellent question.Um, don't have a good answer other than like, we're honest. Just haven't Yeah. This is what the Open AI team does. Okay. Uh, cool. I I I don't have other, like, I, I just, I, I do wanna expand people's minds and also maybe show people if they haven't really done it, but like, I, I think it's very interesting how I sometimes use this more than I use, I mean, I use dia, right?Yeah. Um, I, and I use, uh, I've used like all the other agentic browsers and philanthropic didn't have to build an agentic browser because you just had Claude Cowork and that's enough.Felix: Yeah. I also think like maybe integrating with number of excellent browsers out there, it's like currently on my personal priority list, a little higher than like trying to rebuild a browser from scratch.Yeah. You know, never say never, but I think going back to this idea of like, we wanna plug this into an entire existing workflow, I think our goal is actually to not replace any of the applications we have in your computer. But instead of like, work really well within a new workflow,Alessio: make the new one. Yeah.Are, it seems that nowadays, especially on the browser, most of the innovation is like user ergonomics. It's not really like the underlying browser engine. So I feel like to call it, it doesn't really matter if it's like the, uh, or Chrome or Alice, whatever.Felix: Yeah. We wanna, we wanna meet you wherever you are.Which is like, like obviously I would say that, but it's also just generally true because I don't wanna shrink my potential user base artificially by saying, okay, like, I'm gonna start building for the people who are willing to switch browsers.Alessio: Right.Felix: That's such a, like, you know, like many lawsuits have been filed over who gets to review the browser and like a lot of money has switched hands over the question of like, which browser is default and which search engine is default within the browser.Um, I just wanna build for, yeah, I wanna build for swyx essentially. Like, I wanna, I wanna, I wanna build for people who have a number of annoying tasks that they feel like. Maybe clock could do it. Could do it for them.Alessio: Yeah. What do you think about skills portability? I think there's been one thing, I use another thing called zo, which is kinda like a cloud computer plus agent.And I have a skill to add visitors to the office. Yeah. So whenever somebody has to come in after hours, they need to check in downstairs. Um, but I wanna like text the thing, so it doesn't really work in, in cowork, but now that skill is in the zone harness and it's not in my cowork thing. And then if I make a change, it's gotta, I gotta sync them.How do you see that going? Like I see memory as like. Cloud personal, kinda like, I don't necessarily want my memories to be cross thing.Felix: Yeah.Alessio: But I do want my skills to be cross agent that I use. I think with MTPs, people do the same thing. It's like, oh, Mt. P Gateway. Mt P registry. I don't really know if that's like a business.So I'm curious like if you've had any thoughts in the area.Felix: I think for me, this is sort of where I go back to the really basic primitives for our skills are file-based instead of like this complicated thing that exists inside a place somewhere that is like super proprietary. I'm really leaning into the idea of like, it's all just files and vultures, and that makes it very portable on its own.Right. We do have skills as part of this container format, which was just called plugins.Alessio: Mm-hmm.Felix: And plugins are available both for Claude Code and Claude Code work the same format, and you can install plugins. This works in cowork today. You can basically say, I'm gonna add a whole, like just a GitHub repo as a.Skills marketplace or like a plugin marketplace. And that's how we're doing portability. I think we have a lot of room left to grow in. How do we make it easy for people to know that they can write skills? How do we make it easy for them to just like, share a skill with you? Because obviously all the words I just said, right?Like I'm losing most of the knowledge worker base out there, right. And start by saying, oh, you can connect to GitHub repo. It's not exactly how most people will end up working in like a general knowledge worker space. Um, but I think there's something there. And another thing that's there that I think has not really been properly explored is the, the, the combination of which part of the skill is very portable and then which part of the skill is like very personal to you.Right. And I think that's something we haven't really solved as an industry. Hmm.swyx: It's like, which, how you wanna introduce more structure to the skill or have always have like. Public skill, private skill, you know, pair. Yeah, yeah. Kind of. I think there'sFelix: like a, like the easiest way to do this, which is we do like use string interpolation or something.Right, right. Yeah, yeah. Insert username here, insert like phone number, insert, like known folder, locations, that kind of stuff. Um, that's probably clunky. That's why we haven't built it. Um, but I do think someone is going to come up with like an interesting way to keep everything we like about skills. The portability is just a file, it's just marked down.It's just text, honestly. Right. Like a text file words. The complete lack of structure, which means you don't need any kind of tutorial to write a skill. Just like explain it to Claude the way he would explain it to me and Claude will probably get it before I work. Mm-hmm. Right? You're just like, for booking a flight, tell Claude how to book a flight the same way we tell him somewhere.I just started working here today. But combine that with a very like, personal thing. Um, maybe we'll stick with a booking a flight example. I don't actually think. AI should be booking flights. I think the tools we have is yes.swyx: Yeah. Finally, somebody says it. It's the default demo that everyone's making.Felix: I'mswyx: like, I even against like booking demos, it is not a good showcase.Felix: Yeah. I'm like, I just wanna book my flight myself. But, um, I think there's a lot of things that have a personal and a non-personal component and that's maybe why people reach for flight booking because some things are very universal. Yeah. Super flight is usually better, right? Like few people try to book the most expensive flight.And then some things are quite personal about like what times you prefer, which seat you prefer, which airports you prefer. Combining that and like a skill format that is actually portable, compatible, easy to understand for people. I think that would be very exciting. We just haven't figured it out yet.Alessio: Yeah, I think the text part every, I think everybody by now has some sort of like cloud file thing. Either Dropbox, Google Drive, whatever. So it feels like in a way it should basically like sim link. My skills into all my agent harnesses. Yeah. Just keep those ing like we have internally this like valuable tokens repo, which is like all the commands sub agents.It's good. Uh, and then I build like a TUI where you can start it and be like, you know, install this command and this three sub agents into this agent in this folder and just copy paste this. It doesn't do anything. It literally cp the file into that. But I feel like there should be something similar where like whenever I go into a new thing, it's like, hey, here's like the link to exactly the cloud folder and just bring down these skills into this.Yeah. Like today it doesn't quite work like that. Like if I install a new agent, I cannot, I have to like copy paste all the skills and I don't even know where they are.Felix: Yeah.Alessio: That's like the big problem. It's like where do I find them?Felix: Yeah.Alessio: Um, so I'm curious like in the future like that, that almost feels like my personal productivity thing will be my skills.Felix: Yeah.Alessio: Is not really the product that I use. Everybody has access to the same product. But today there's, that just looks like copy pasting ME files, IFelix: think so many things I, I really like thinking about agents and LLMs just as like another coworker. So many attempts have made to build documentation companies that are like, oh, we're gonna solve oil documentation problems.Um, I myself, like spend a little bit of time working in notion, right? I'm like deeply familiar with the concept of let's get everyone on the same page. Mm-hmm. Right? And what you're basically saying here is you want all your agents to be on the same page about your preferences, about the skills, about the way they ought to work and like how they ought to execute.And I'm not sure what the right thing is going to be if it's going to be some, some company that can say, all right, we're as an independent body, we're not trying to like, push into any particular product. It's our job to be like the skill authority, and we provide, I don't know, we're gonna be the Dropbox of skills and we can just sim link us into all the products we want to use.I'm not sure that's gonna be viable business, but as, as an idea, it would be cool.Alessio: Yeah. Yeah. I think so many things are just going away as businesses. It's like, how am I supposed to do it? I'm not even asking somebody to make a product about it. Like yeah. I wanna personally know. And there's things like you said, it's like you almost wanna skill and then interpolate it between personal and work.So if I'm booking a fly for work, it's different than I'm booking a flight personally.Felix: Yeah.Alessio: In some ways, yeah. But like a lot of the scaffolding is the same, you know? Cool.Felix: I mean, as an engineer I will tell you like, you know, technic a person to technic a person. I will just be like siblings.Alessio: Well that's what, that's what I do.We call that MD and agents that MD's just the same how sim length. And so it is like, that works, but it feels like, yeah, I don't know. MaybeFelix: you can always go one, you can always tell cowork problem and then cowork will solve it for you. Just make the siblings. That's like one way to do it.Alessio: That's true.That's true. All right. Everything is called cowork.Felix: Uh, potentially spicy. Question for both of you.swyx: Uh, which of these industries will go away?Alessio: Okay, so what Felix was saying before is interesting. There's busy like. The short term pressure of like, we need to turn these tokens into valuable things, which is I should build the last mile product that harness the model.And then there's the question of like, long term, which ones are gonna still be valuable? And I think you're kind of seeing this today with like, uh, you know, the coding space in a way is kind of like everybody's moving up and up in stack because you need more than just turning tokens into code. I think search, like enterprise search is kind of saying the same thing.Like with G Clean and like all these different companies is like, at the end of the day, if Cowork is the one doing all the work, the search itself is like such a small part that like, I don't know if I'm really gonna pay that much money just to do search. It's almost like everything is like a cowork vertical.So like how much can cowork first party support?swyx: Mm-hmm.Alessio: And how much can it not? I think for a lot of these things, the planning thing that you were showing do Which one? The planning. The planning.swyx: Okay. Yeah. Yeah.Alessio: That's one thing where like most of the value that these agents provide is like they're better at planning for specific tasks.Yeah. And have better tools for it.swyx: Yeah.Alessio: But I think the models are now moving in that direction and they have the right harnesses and they're on your computer. So for me it's almost like if for the end customer trusts your startup to be the provider of that task result, then I think that works. This is, uh, something that, this is a shortswyx: spike that we're, we're working on.Uh, yeah.Felix: I think, look, I'll, I'll, I'll tell you this, like I don't think I'm the best person to like actually estimate which industry is going to be hit the hardest. But I do think that at philanthropic as a group of people, we're deeply worried about the impact. That the tools are going to have on the labor market, especially for like junior employees that, because I think, I think it's only honest to say that when we talk about automating a lot away, a lot of the work that we personally find annoying that we maybe think's not the best use of our time.In a lot of industries, that kind of work would've been given to a junior entry level employee. Yeah. Right. And I think it's, it's only, it's only right to be really worried about that and like worry what that's going to do in particular to people like enter the shop market.Alessio: Mm-hmm. I have a solution for that.Which you make them, you create simulative jobs for them.Felix: Okay.Alessio: So this is, this is like half joke, half true. So if you think about software engineering, when you're like a junior engineer, you work like 1, 2, 3 years. And in those three years there's like maybe like a handful of moments where like you really learn something.And then a bunch of other days where like you're not really progressing.Felix: Yeah.Alessio: I think now we can use AI and these models to actually like shortcut these careers and almost like simulate the early years of your work and like just make them like super dense and like these learnings, it's like, hey, we're working on this feature, which is like a distributed system and you need to learn this thing that might take three months at a company.And so you take three months here, it's like we're just simulating the whole thing. It's actually not a real thing. And in one week we kind of speed run through the whole thing and you kind of learn your lesson from there. And we kind of repeat that in like one year. You basically get like three years worth of like projects and experience.Yeah. I think it's harder for like things like sales or for things like, you know, marketing because you don't really have a way to get the feedback loop. But I think a lot of it, it sounds kind of silly, it's like you're making the new effect job, but it's almost like you go to college, right? People pay to learn how to do it, and this might feel similar where it's like, hey, we have the.Jane Street Simulator is like, you wanna come work at Jane Street? We'll just put you in the simulator for like three months.Felix: Wow.Alessio: And you'll come out of it. It's like, you know, I'm ready.Felix: So there, there is an aspect here. I'm not an expert enough to like actually know what, what is going to happen to marketing or legal or finance, right?Like, I don't work in those jobs and I, I don't think I should talk about them, but I am an engineer and I think I have a pretty good idea of what engineering is like. And I think one thing we're sort of seeing is that as a company and also as, as the public, we're like deeply worried about entry level, but we're also seeing more senior engineers accelerate it.If like they're more productive. They, they actually increase the value they provide. And the thing that I'm thinking about a lot is the fact that even before all of this happened, um, I've always had a lot of respect for the University of Waterloo and the, the new grads that have joined my teams as from coming from the University of Waterloo always felt like.More ready than new grads will like literally spend their entire time at the university regardless of how good, but never actually had to work inside an environment where you have to ship things that eventually will be used by users. And I'm, I'm, I'm German. I like initially went to German University and I think the, the, the like information systems programs, there tend to be very theoretical, right?Like I often give people the example of like trying
What would it mean to disentangle humanities scholarship from combative, extractive, and colonial ways of knowing and writing? This is the question that animates Quiet Methodologies: Humility in the Humanities (U Minnesota Press), the latest book by literary scholar and poet Suzanne Bost. Quiet Methodologies isn't a traditional work of literary scholarship. Instead, the book reaches toward alternative ways of thinking with and teaching literature, grounded in speculation and conversation. It models a quiet kind of humanities work, committed not to asserting answers but to asking questions, not to claiming mastery but to embracing uncertainty. For all its quietness, then, Quiet Methodologies is a bold and challenging work. Speaking to a moment of crisis within and beyond the academy, its provocations and explorations will be of interest to scholars and students working across humanities disciplines. In conversation with Alix Beeston, Bost shares about the literary archives and scholarly works that helped her to unlearn scholarly conventions. She sets out her vision for reimagining humanities labor in terms of ethical responsibility, receptiveness, care—and even, perhaps, love. Learn more about your ad choices. Visit megaphone.fm/adchoices Support our show by becoming a premium member! https://newbooksnetwork.supportingcast.fm/new-books-network
This Women in History Mini-Series episode with Dr. Victoria Bateman explores the groundbreaking work of Anna Schwartz, a pioneering economist who transformed macroeconomics through data-driven research. Discover how her meticulous analysis of monetary history shaped economic policy and the legacy she left for future generations.Chapters00:00 Introduction to Anna Schwartz and Her Impact01:45 The Historical Context of Economic Data04:10 Challenges Faced by Women in Economics06:03 A Monetary History of the United States09:04 The Methodology of Anna Schwartz11:46 Legacy and Personal Insights on Anna SchwartzFollow Breaking Math on Substack (https://breakingmath.substack.com/) Twitter (https://x.com/breakingmathpod) Instagram (https://www.instagram.com/breakingmathmedia/) Bluesky (https://bsky.app/profile/breakingmath.bsky.social) Website (https://www.breakingmath.io/) YouTube (https://www.youtube.com/@BreakingMathPod) Follow Victoria on Website (http://www.vnbateman.com/)Instagram (https://www.instagram.com/women.wealth.power/) Twitter (https://x.com/vnbateman) Bluesky (https://bsky.app/profile/vnbateman.bsky.social) Follow Autumn on Twitter (https://x.com/1autumn_leaf) Bluesky (https://bsky.app/profile/1autumnleaf.bsky.social) Instagram (https://www.instagram.com/1autumnleaf/) Substack (https://substack.com/@1autumnleaf) TikTok (https://www.tiktok.com/@1autumn_leaf_)
This episode kicks off a brand new podcast mini-series, called "Sell Now" aimed to help you make sales in your business faster and easier. Today, Jill introduces the concept of methodology as a key driver of easier sales. There's a difference between a macro method, which is your high-level coaching philosophy and big "dial movers" that define your overall brand, and a micro method, which is a specific, named roadmap built into each individual product or program. Today's buyers don't want massive, months-long courses; they want targeted micro solutions to micro problems, and when you package your expertise into a memorable system or framework, you make the intangible tangible. Get on the Interest List for Jill's brand new offer, Mini Course Mastery! https://jillfitfree.com/mini-course-waitlist/ Get on the waitlist for FBA: https://jillfitfree.com/fba-waitlist/ Jill is a fitness professional and business coach who effectively made the transition from training clients in person and having no time to build anything else to training clients online and actually being more successful. Today, Jill helps other coaches to do the same. Connect with me! Instagram: @jillfit | @fitbizu Facebook: @jillfit Website: jillfit.com
Proof changes everything. When the world serves you endless "hot takes" about health, habits, and mindset, we need to slow down and build on what actually holds up—methods that work across people and across time. Today we unpack why evidence-backed tools make personal growth more predictable, less stressful, and far more sustainable, and we put 3 practical techniques in your hands so you can start reshaping your limiting thinking and story-telling right away. You'll learn how to build a confidence stock—an ongoing log of small wins and improvements that counters your brain's negativity bias and grows self-efficacy. We then pressure-test the stories you tell yourself with a clean filter: does this belief serve you? If holding it for a year shrinks your action and your world, it's time to rewrite it toward utility, practice, and progress. Finally, we explore self-distancing—third-person self-talk that lowers emotional heat and boosts clarity. This simple shift moves decision-making into a calmer part of your brain, so you can see options, choose a next step, and act with less friction. Along the way, we highlight how modern, science-backed approaches deliver the predictability you need to navigate fast change without drowning in noise. The result: fewer yo-yo fixes, more consistent outcomes, and a sturdier path to the future self you're building. If this resonates, share the episode with one friend who's stuck in a limiting story, then subscribe and leave a quick review to help others find us. Text Me Your Thoughts and IdeasSupport the showBrought to you by Angela Shurina Behavior-First, Executive, Leadership and Optimal Performance Coach 360, Change Leadership & Culture Transformation Consultant
Brand building and business skill development are not the same, so it's important for internet entrepreneurs not to get distracted by shiny-object marketing tactics like miracle funnels and ad scripts at the expense of the bigger picture. Today Jill shares her "three M's" framework for building a powerful personal brand—Mastery (expert content), Methodology (your signature system), and Me (personal, human stories). A strong brand is an anti-fragile asset that compounds over time, while duct-taped-together strategies are easily disrupted by algorithm changes or shifting buyer behavior. Granular tactics like A/B testing, copy optimization, and funnel building absolutely have their place, but only as skills developed alongside consistent brand-building, not as substitutes for it. Get on the waitlist for FBA: https://jillfitfree.com/fba-waitlist/ Join the Strategy Lab: https://www.jillfitprograms.com/the-strategy-lab Jill is a fitness professional and business coach who effectively made the transition from training clients in person and having no time to build anything else to training clients online and actually being more successful. Today, Jill helps other coaches to do the same. Connect with me! Instagram: @jillfit | @fitbizu Facebook: @jillfit Website: jillfit.com
Gregory Zuckerman introduces the brilliant, driven scientists pursuing vaccines for AIDS, cancer, and malaria, who pivoted their controversial methodologies to confront the burgeoning COVID-19 pandemic. 3
Krista Stepney shares powerful tactics for moving forward when fear has you feeling stuck.— YOU'LL LEARN — 1) How to identify and address the root causes of inaction2) How to take your power back from comparisons and self-doubt3) Two powerful scripts for when you're stuckSubscribe or visit AwesomeAtYourJob.com/ep1130 for clickable versions of the links below. — ABOUT KRISTA — Krista D. Stepney is a leadership and business strategist, keynote speaker, and transformation advisor who helps leaders and everyday changemakers turn hesitation into momentum. With over 15 years of experience in operations, organizational leadership, and culture transformation, Krista blends research, faith, and lived experience to help others build a purposeful life and legacy.As the creator of The BOLDprint Method and the W.A.N.D. Methodology, she has coached executives, entrepreneurs, and everyday dreamers on overcoming fear, resisting comparison, and designing a personalized roadmap forward, even when the next step feels unclear.Her mission is simple: to help people get unstuck and move anyway, especially when it feels like the hardest thing to do.• Book: Move Anyway: A Guide for Overthinkers, Perfectionists, and Almost-Starters• Website: KristaStepney.com— RESOURCES MENTIONED IN THE SHOW — • Study: Perfectionism Research by Vitale & Co.• Study: “Healthy Reflections: The Influence of Mirror Induced Self-Awareness on Taste Perceptions” by Ata Jami• Study: “Implementation Intentions and Goal Achievement: A Meta‐analysis of Effects and Processes” by Peter M. Gollwitzer and Paschal Sheeran• Book: Getting Things Done: The Art of Stress-Free Productivity by David Allen• Book: Professional Troublemaker: The Fear-Fighter Manual by Luvvie Ajayi Jones• Past episode: 015: David Allen, The World's Leading Authority on Productivity• Past episode: 798: How to Have Difficult Conversations about Race with Kwame Christian• Past episode: 1078: How to Stop Playing Small and Achieve Your Greatest Goals with Richard Medcalf— THANK YOU SPONSORS! — • Monarch.com. Get 50% off your first year on with the code AWESOME.• Shopify. Sign up for your $1/month trial at Shopify.com/better• Factor. Head to factormeals.com/beawesome50off and use the code beawesome50off to get 50% off and free breakfast for a year. (New Factor subscribers only)See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
© 2020-2026 Ivy Podcast Discovery LLC
