<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Stevie Kim on Medium]]></title>
        <description><![CDATA[Stories by Stevie Kim on Medium]]></description>
        <link>https://medium.com/@StevieLKim?source=rss-9b24350854e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dA94GMFClVIxPo2oOzqMXQ.jpeg</url>
            <title>Stories by Stevie Kim on Medium</title>
            <link>https://medium.com/@StevieLKim?source=rss-9b24350854e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:34:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@StevieLKim/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Your Activation Metric Is a Guess. Act Like It.]]></title>
            <link>https://medium.com/@StevieLKim/your-activation-metric-is-a-guess-act-like-it-65b9214ebd16?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/65b9214ebd16</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-analytics]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[activation-metrics]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 15:21:01 GMT</pubDate>
            <atom:updated>2026-10-13T00:37:59.817Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve watched teams make the same mistake more than once.</p><p>They pick an activation metric because it’s easy to measure. Usually, it’s something users have to do to get started: create a project, configure an account, invite teammates, or connect a data source.</p><p>That action then becomes the definition of activation. Say the team chooses creating a project as its activation event. Pricing gets built around that same unit: five active projects on the free plan, 100 on Pro, and unlimited projects on Enterprise.</p><p>Everyone agrees on the numbers. The feature ships.</p><p>But nobody has answered this question: <strong>Does completing that action mean the customer actually experienced value?</strong></p><p>I’ve seen what happens when teams skip that question.</p><p>On one product I worked on, the agreed-upon activation metric measured a configuration action. I tracked it, but I also looked at what users did afterward.</p><p>What caught my attention wasn’t the configuration. It was how users engaged with the insights the product generated, which was information they could use to make decisions.</p><p>The configuration was necessary to get started, <strong>but it wasn’t the payoff</strong>.</p><p>That observation didn’t prove I’d found a better activation metric, howeveer it did give me a reason to question the one we were using. The bigger problem was that we hadn’t documented why we’d chosen that metric in the first place. We had a definition, but no clear hypothesis connecting the behavior to customer value.</p><p>And without a hypothesis, how do you know when your activation metric is wrong?</p><h3>First, What Are We Actually Measuring?</h3><p>Three concepts often get lumped together in activation conversations.</p><p><strong>The aha moment</strong> is when a user recognizes that your product can help them accomplish something important. It’s subjective. You can investigate it through interviews and behavioral evidence, but you can’t directly capture someone’s realization in an analytics event.</p><p><strong>The activation event</strong> is an observable behavior you believe indicates that a user has experienced initial value. It’s a measurable proxy for the aha moment, not necessarily the moment itself.</p><p><strong>The customer outcome</strong> is the result the customer ultimately wants. It might be finishing projects faster, saving money, or reducing errors. These outcomes often take much longer to materialize.</p><p>Let’s use a fictional project management product.</p><blockquote>A customer creates a project, adds five teammates, and configures a workflow.</blockquote><p>They’ve completed onboarding. But have they gotten anything useful yet?</p><p>Now imagine the platform analyzes their project and recommends how to allocate people across tasks. The customer applies that recommendation.</p><p><strong>For the first time, the product has helped them make a decision.</strong></p><p>That seems like a much stronger activation signal than creating a project.</p><p><strong>But it’s still a hypothesis.</strong></p><p>Maybe customers who apply recommendations finish projects faster. Maybe they don’t. Maybe the teams that use recommendations were already better organized.</p><p><strong>We need evidence</strong> before we decide we’ve found the right behavior.</p><h3>Write the Activation Hypothesis Down</h3><p>Before selecting an activation metric, I think teams should be able to complete a statement like this:</p><blockquote>We believe [persona] experiences initial value when they [specific behavior] within [time window], because it helps them [job to be done]. We expect that behavior to be associated with [customer outcome].</blockquote><p>For our fictional project management tool:</p><blockquote>We believe <strong>project managers</strong> experience initial value when they <strong>apply a staffing recommendation </strong>to a <strong>live project within their first two weeks</strong>, because it helps them <strong>allocate resources more effectively</strong>. Over time, we expect those projects to experience <strong>fewer scheduling delays</strong>.</blockquote><p>This gives us something concrete to test.</p><p>We have a specific user, an observable behavior, an initial measurement window, and an outcome we expect the behavior to predict.</p><p>Notice that the behavior and outcome are different.</p><blockquote>We can instrument the platform’s recommendation and apply it immediately.</blockquote><blockquote>We hope to observe fewer scheduling delays later.</blockquote><p>We shouldn’t have to wait months to measure early product usage. But we also shouldn’t assume that completing an in-product action means the customer achieved their goal.</p><p><strong>The activation event tells us what users did. The outcome helps tell us whether it mattered.</strong></p><p>Before someone turns “within two weeks” into an official KPI, that window needs scrutiny too.</p><p>A daily-use product might reasonably expect users to experience value in their first session. A monthly reporting tool might need several weeks.</p><p>The right window depends on how customers naturally use the product, not on which interval makes the dashboard look good.</p><h3>How Do You Know If You Picked the Right Metric?</h3><p>Before launch, your activation definition is largely a hypothesis informed by research, customer understanding, and whatever evidence you already have. Once you have enough usage data, you can start testing it. If you don’t have data yet, make your best guess, then get to tracking!</p><p>Suppose our fictional project management product has been live for six months.</p><p>We want to know whether applying a staffing recommendation is a useful activation signal.</p><p>We could look at new accounts, record which actions they completed in their first two weeks, and compare their day-90 retention.</p><p>Here’s what this might look like:</p><figure><img alt="Hypothetical product activation numbers" src="https://cdn-images-1.medium.com/max/1024/1*HgqQbOoJSd-uASTG72MPkA.png" /></figure><p>These numbers are hypothetical, but the distinction is important. Creating a project barely separates retaining accounts from those that don’t. Applying a staffing recommendation shows a much stronger association with retention, which makes it an interesting candidate for activation.</p><p><strong>Note: it doesn’t prove that applying the recommendation causes retention.</strong></p><p>More engaged customers tend to do more of everything. They may be more likely to apply recommendations <em>and</em> stick around for reasons unrelated to that feature.</p><p>That’s a confounding problem.</p><p>We also need to make sure we’re comparing accounts fairly. Everyone needs the same opportunity to complete the activation event and reach the retention checkpoint. <strong>Customer segment, acquisition channel, and account size might also explain some of the difference.</strong></p><p>So the initial analysis tells us where to investigate. It doesn’t settle the question.</p><h3>Test What Happens When More Users Reach That Behavior</h3><p>One way to get stronger evidence is to experiment with onboarding.</p><p>Randomly assign new accounts to two groups. The <strong>control group</strong> gets the existing onboarding experience. The <strong>treatment group</strong> gets an onboarding experience designed to help them reach and apply a staffing recommendation sooner.</p><p>Then measure two things:</p><ul><li>Did more accounts apply a recommendation?</li><li>Did those accounts also show better retention or customer outcomes?</li></ul><p>If the treatment increases both the recommendation usage and downstream results, that’s stronger evidence that <strong>helping users reach this behavior creates value.</strong></p><p>If recommendation usage increases but retention doesn’t change, we need to investigate. Perhaps applying a recommendation predicts which customers will stick around, but encouraging more customers to do it doesn’t improve their experience. Perhaps we’re encouraging the action before customers are ready. Or perhaps retention isn’t the right outcome for evaluating this particular feature. The distinction matters.</p><p><strong>A behavior can predict retention without being the reason customers retain.</strong></p><p>For an activation metric, I want evidence that the behavior is meaningfully connected to value, not just that it’s easy to drive up.</p><h3>Don’t Confuse the Activation Target With the Activation Metric</h3><p>Even after choosing a behavior, we still need to decide what success looks like.</p><blockquote>Suppose 20% of new accounts apply a staffing recommendation within two weeks.</blockquote><p>Is that good or bad? We don’t know yet.</p><p>We need a baseline, an understanding of the customer’s expected usage pattern, and some evidence of what the behavior predicts.</p><p>Setting a target of 40% might be reasonable, but we should be clear that it’s an improvement target, not proof that 40% is the right activation rate.</p><p><strong>I also think teams should document what would prompt them to revisit the hypothesis.</strong></p><p>For example, we might agree to investigate if:</p><ul><li>Very few qualified customers reach the event, even after we address obvious onboarding friction.</li><li>The event shows little relationship to retention or customer outcomes.</li><li>Research repeatedly shows customers experience their first meaningful value elsewhere.</li></ul><p>None of these observations automatically invalidate the metric, but they’re reasons to look more closely.</p><p>And before any analysis starts, there’s another detail worth getting right: the denominator.</p><p><strong>Are we measuring activation as a percentage of all signups, qualified signups, accounts, or individual users?</strong></p><p>Those choices can produce wildly different rates. Pick the population you actually intend to serve, define the measurement window, and keep those definitions consistent. Otherwise, you can improve your reported activation rate without improving the product.</p><h3>What If Different Customers Experience Value Differently?</h3><p>This is where activation gets more complicated, especially in products serving multiple roles.</p><p>Our project manager might experience value by applying a staffing recommendation.</p><p>A data scientist using the same platform might experience value by finding a quality problem before it affects a project.</p><p><strong>Different jobs, different behaviors, different moments of value.</strong></p><p>That doesn’t necessarily mean we need to force both behaviors into one activation event.</p><p>We might track activation separately by persona. Or, if the product’s value genuinely depends on multiple people collaborating, we might define activation at the account level.</p><p>For example, if a project’s success depends on both resource planning and quality monitoring, a meaningful account-level milestone may involve both activities. But requiring both actions just because both personas exist would be another guess.</p><p><strong>The definition should follow how value is delivered, </strong>not how neatly we want the metrics to fit into one dashboard.</p><h3>What Happens When the Data Disagrees With You?</h3><p>Finding the right activation behavior is only part of the job. We also have to figure out why customers aren’t reaching it, or why reaching it isn’t producing the results we expected.</p><p>A few situations are worth separating.</p><blockquote>Users reach the activation event and continue getting value.</blockquote><p>Good. Now we can look at time to value.</p><p><strong>How long does it take customers to reach that first meaningful experience? Where do they get stuck? What can we remove or simplify?</strong></p><p>This is where onboarding improvements can have a meaningful effect.</p><blockquote>Users reach the activation event but don’t retain.</blockquote><p>Maybe our activation event isn’t as meaningful as we thought. Maybe the product delivers initial value but not enough recurring value. Or perhaps customers leave for reasons unrelated to the experience.</p><p>We need to investigate before deciding to add more features.</p><blockquote>Users rarely reach the activation event.</blockquote><p>This could be an onboarding problem, but it could also be an acquisition problem.</p><p>Maybe the path is too complicated. Maybe customers don’t understand what the product can do. Or maybe we’re attracting people whose needs don’t match the product.</p><p>Session recordings, funnel analysis, and customer interviews can help distinguish these possibilities.</p><blockquote>Users keep returning for something we didn’t consider central to the product.</blockquote><p>Pay attention.</p><p>If customers repeatedly find value in a supposedly secondary feature, that may be telling us something important about the <strong>product’s actual value proposition</strong>.</p><p>Don’t dismiss that behavior because it doesn’t match the original roadmap.</p><h3>Before You Redesign Onboarding, Look at Acquisition</h3><p>A low activation rate doesn’t always mean onboarding is broken.</p><p>Imagine two acquisition channels.</p><blockquote>One consistently brings in customers who understand the problem your product solves. Most of them activate.</blockquote><blockquote>The other brings in large volumes of signups, but very few customers ever reach the first meaningful product experience.</blockquote><p>Blend those channels together, and the overall activation rate might look mediocre.</p><p>You could spend months redesigning onboarding when the bigger issue is that one channel is acquiring the wrong audience.</p><p><strong>That’s why I want to see activation broken down by acquisition source, customer segment, and other meaningful cohorts before drawing conclusions.</strong></p><p>It also <strong>creates an organizational problem</strong> when marketing is rewarded for signup volume while product is held accountable for activation.</p><p>Both teams can hit their targets while the business gets nowhere.</p><p><strong>A shared measure</strong>, such as qualified activated accounts, can help align acquisition with the customers who are actually likely to benefit from the product.</p><p>The point isn’t to make marketing responsible for every onboarding problem. It’s to stop treating signup volume as success when those signups don’t turn into customers who receive value.</p><h3>One More Trap: Building Pricing Around an Unproven Metric</h3><p>Remember the team that selected a setup action as its activation event?</p><p>That decision can get particularly expensive.</p><p>Suppose we define activation as inviting teammates, and then build pricing tiers around the number of teammates an account can invite.</p><p>Free accounts get three seats. Paid accounts get more.</p><p>Seat-based pricing isn’t inherently wrong (often it is, but let’s not digress). The problem arises if customers need more than three people to experience the product’s core value.</p><p><strong>Now the paywall appears before the payoff.</strong></p><p>We’ve limited the action customers need to take before they have enough evidence to decide whether the product is worth paying for. And if we’ve also defined that same action as activation, we now have two decisions built on the same untested assumption.</p><p>Revising the activation metric becomes entangled with pricing.</p><p>Activation and pricing don’t have to use different units. Sometimes the same usage measure genuinely reflects both early value and willingness to pay.</p><p>But they answer different questions.</p><p>Activation asks: <strong>Has the customer experienced enough value to recognize why this product matters?</strong></p><p>Pricing asks: <strong>What are customers willing to pay for, and how should we package that value?</strong></p><p>Treating them as interchangeable without testing the assumptions leads teams to optimize for the wrong behavior.</p><h3>Your Activation Metric Should Be Allowed to Change</h3><p>Teams don’t need to find a perfect activation metric before launching.</p><p><strong>They need a plausible hypothesis, a way to measure it, and a willingness to change their minds.</strong></p><ol><li>Start with what you know about the customer and the job they’re trying to accomplish.</li><li>Identify an early behavior that might indicate they’ve experienced value.</li><li>Write down why you believe that behavior matters and what downstream results you expect.</li><li>Instrument it, study real usage, and test whether helping more customers reach that behavior actually improves something meaningful.</li><li>Then revisit the definition as your product and customers change.</li></ol><p>An activation metric that predicted retention a year ago may become less useful as you add features, attract different customers, or change your positioning.</p><p>The mistake isn’t starting with a guess.</p><p><strong>It’s forgetting that you started with one.</strong></p><p>Once you’re confident customers reach that first meaningful moment of value, another question arises: do they come back to experience it again?</p><p>That’s retention and habit formation, and it deserves its own article.</p><h3>About Me</h3><p>I’m a product manager and hands-on product builder focused on AI products, user experience, and growth. My work spans agentic workflows, analytics, experimentation, and improving how customers discover and experience product value.</p><p>You can find me on <a href="https://github.com/stevielkim">GitHub</a> or connect with me on <a href="https://www.linkedin.com/in/stephanielkim/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65b9214ebd16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimize Your AI Prompts Without Breaking the Brain Bank]]></title>
            <link>https://medium.com/@StevieLKim/optimize-your-ai-prompts-without-breaking-the-brain-bank-f4e5fa3d9e72?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4e5fa3d9e72</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai-product-management]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 16:20:01 GMT</pubDate>
            <atom:updated>2025-06-27T22:37:25.525Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4GInhqITe4x7F_3icb91nw.png" /><figcaption>ChatGPT generated image</figcaption></figure><p>Recently, while listening to <a href="https://www.lennysnewsletter.com/p/ai-prompt-engineering-in-2025-sander-schulhoff">Lenny’s Podcast featuring Sander Schulhoff,</a> I found myself nodding along as he debunked some persistent prompt engineering myths, particularly the idea that assigning roles or backstories to LLMs meaningfully improves output.</p><p>I’d noticed the same thing.</p><p>While working on <a href="https://medium.com/@StevieLKim/automating-seo-with-crewai-3e34407226c1">multi-agent workflows in CrewAI</a> and during conversational prompting with ChatGPT, I kept seeing advice that felt more like folklore than fact. Supposedly, if you give your agents impressive titles, motivational pep talks, and spell out the “importance” of their task, they’ll magically generate better responses.</p><p>But in my experience? That kind of prompt padding either had no effect or made results worse.</p><h3>Prompting Theater vs. Practical Results</h3><p>There’s nothing quite like implementing every “expert” trick you’ve read then watching the model’s performance tank. And thanks to our quirky human brains (hello, cognitive bias and sunk cost fallacy), I stuck with those techniques longer than I should have.</p><p>After dozens of iterations, which of course I didn’t use version control for (oops), I finally stripped my agents’ prompts back down to their simpler, earlier forms (thanks to VisuaCodeStudio’s Timeline). Only then did performance improve enough to start layering in more complexity such as changing agent architecture from sequential to hierarchical flows or developing custom tools or changing collaboration between agents.</p><p>Lesson learned: <strong>track your changes and results</strong> it’s the only way to see what’s really moving the needle. For me at least, it’s more intuitive to commit code changes, but when it’s “just” natural language instructions, I tend to forget to treat prompts as code too. But it’s easier (at least for me) to rewrite a function I stripped out than to remember exactly what I said and how I said it in prompt form.</p><h3>Better Guidance: Chunk, Reflect, and Critique</h3><p>One of the <a href="https://youtu.be/eKuFqQKYRrA?si=zZQ-7hIUAXzkeuem">insights Schulhoff shared</a>, and which <a href="https://docs.crewai.com/quickstart">CrewAI</a> has built into its framework, is the value of having agents break down their tasks (decomposition), reflect on their work, and critique the outputs. These techniques along with refining your prompts with clear instructions, examples of expected outputs, and even what not to do, produce much more consistent improvements than the role-based storytelling gimmicks.</p><p>So my advice, save your energy and don’t bother with complex roles and backstories which you can think of as system-level prompts. Instead, put your time into crafting clear instructions with appropriate examples at the user-prompt level in your <a href="https://docs.crewai.com/concepts/tasks">CrewAI Tasks</a>, <a href="https://langchain-ai.github.io/langgraph/concepts/low_level/">LangGraph Nodes</a> or conversational prompts into your favorite LLM.</p><h3>Few-Shot Prompting: Economies of Scale</h3><p>One thing that Schulhoff mentioned that I should test more of is providing additional context with few-shot prompting. In my experiments with CrewAI, I’ve mostly avoided detailed examples. When I’ve refined my prompts, I usually provide bullet points listing what to include (or not to include), vs full-length labeled samples that include reasoning to provide more context.</p><p>Honestly, when I have to write complete examples of outputs or provide labeled data, it starts to feel like I’m doing the work I “hired” the LLM/agents to do. This might seem counterintuitive coming from someone who has hand labeled training data and built ML models themselves (and later worked at a data labeling software company), but for small scale updates or when you don’t know what the output should be (such as reports or research), then I think it might be overkill. Like everything in life, it depends.</p><p>If you’re <a href="https://medium.com/@StevieLKim/automating-seo-with-crewai-3e34407226c1">optimizing SEO</a> across dozens of blog posts or automating changes for 20-plus documents, a few well-structured examples can significantly improve consistency and reduce manual effort over time. Like Schulhoff mentioned, his workflow evolved from low accuracy zero-shot prompting to few-shot prompts with a few coded medical documents. But in my case, I’ve only automated a handful of documents to optimize for SEO, where the risk of error is low and the payoff for heavy prompt engineering is minimal. When the scope is limited, over-investing in few-shot examples starts to look more like premature optimization than strategic leverage.</p><h3>Potential Tradeoffs of Few-Shot Learning</h3><p>Something that I noticed, but didn’t track closely, is when I provided overly specific examples for my SEO multi-agentic workflows, the output degraded in quality and at times failed to follow even simple instructions.</p><p>This got me wondering: <strong>can too many or overly specific examples limit creativity?</strong> Can the model start to overfit?</p><p>For instance, suppose I provide a sample SEO-optimized blog title like:</p><p><em>“Use AI to Optimize SEO Blog Posts”</em></p><p>Then I ask the LLM to rewrite it using long-tail keywords, resulting in:</p><p><em>“Automating SEO Medium Posts with CrewAI Agentic Workflows”</em></p><p>Now imagine a workflow that applies this pattern across all my blog posts. Would the LLM start overusing phrases like “SEO,” “CrewAI,” or “workflow,” even in contexts where they don’t belong? Could a title like:</p><p><em>“The First Five Minutes: Finding the Hook in Reddit’s Onboarding Flow”</em></p><p>be transformed into:</p><p><em>“Finding SEO in Reddit’s Onboarding Flow with CrewAI”?</em></p><p>(Okay, not my finest title, but you get the idea.)</p><p>This kind of prompt overfitting isn’t something I’ve deeply tested yet, but it raises important design tradeoffs. The more examples you give, the more you shape the output, but also the narrower that output may become. It’s something to keep in mind, especially when working on tasks that require variation, creativity, or voice. For more information by folks who have considered this more than I have, check out <a href="http://twitter.com/arbaazkan96">@arbaazkan96</a> <a href="https://medium.com/@arbaazkan96/challenges-in-prompt-engineering-overfitting-1ca1179aafff">blog post</a> on overfitting or <a href="https://www.datacamp.com/tutorial/few-shot-prompting">DataCamp’s prompt engineering post</a>.</p><p><strong>Forget the Theater Do What Works</strong></p><p>If you’re working with LLMs or agentic frameworks like CrewAI, don’t fall into the trap of prompt theater. Forget the backstories. Skip the role-playing. Instead, focus on simple, functional instructions and build from there with structure, critique, and iteration.</p><p>You don’t need a PhD in Prompt Whispering. You just need a system and a willingness to test what actually works.</p><p><strong>About Me</strong></p><p>I’m a product strategist and former ML PM who helps teams cut through AI hype and focus on what actually works. From prompt optimization to multi-agent orchestration, I experiment with LLM workflows to uncover repeatable patterns that drive usability and impact. I also support teams with product operations: from streamlining roadmaps to aligning cross-functional priorities and scaling experimentation practices. My background spans AI infrastructure, developer tools, and product-led growth.</p><p><strong>Need a fresh perspective on your AI roadmap, agent workflows, or product ops stack?</strong><br>Let’s talk. Check out my <a href="http://stevielkim.com/">portfolio</a> and connect with me on <a href="#">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4e5fa3d9e72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Product Thinking Approach to Real Estate Due Diligence]]></title>
            <link>https://medium.com/@StevieLKim/a-product-thinking-approach-to-real-estate-due-diligence-26951aa86096?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/26951aa86096</guid>
            <category><![CDATA[real-estate-investments]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[risk-assessment]]></category>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Fri, 13 Jun 2025 14:26:38 GMT</pubDate>
            <atom:updated>2025-06-13T14:26:38.812Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Sweating real estate buyer with a discolsure form in their hand" src="https://cdn-images-1.medium.com/max/1024/1*ZqdZ1wWnVTySLYoGMjVTmg.png" /><figcaption>Generated by ChatGPT</figcaption></figure><p>Buying a home or investment property is stressful, even for experienced buyers. It’s easy to overlook risks buried in legal documents or inspection reports, especially when urgency takes over. I’ve been there, and it’s what inspired me to explore a smarter way to help buyers protect their ROI by reading between the lines, literally.</p><p>This post shares lessons from a side project where I applied product discovery techniques to a problem I personally encountered: buyers missing critical information hidden in seller disclosure and inspection documents.</p><h3>Real Estate Due Diligence: Risk Isn’t Always Obvious</h3><p>When you’re under pressure to act fast, whether from bidding wars or financing deadlines it’s easy to skim dense documents like seller disclosures. But risk doesn’t always announce itself. It hides in contradictions, omissions, and vague checkboxes.</p><p>For example, a seller might check “No” to pest problems… yet also say they hired pest control just last year. If you’re not cross-referencing responses or reading closely, you’ll miss clues that something isn’t adding up.</p><p>That kind of mismatch was the spark behind my project idea: a smarter way to detect risk by helping buyers interpret document inconsistencies.</p><h3>The Insight That Sparked the Idea</h3><p>I bought a house that looked great at first glance. Newly remodeled interior, great location, but zero curb appeal, and it had sat a long time on the market. That meant I could get a good deal in a crazy hot sellers market. But after closing, I started uncovering hidden issues I <em>could have</em> spotted had I better cross-checked the seller disclosure with the inspection report.</p><p>That’s when I realized the problem wasn’t just buried in the documents, it was buried in <em>how</em> we interpret them under time pressure. Most tools help you analyze comps or calculate cash flow, but few offer help when it comes to interpreting the actual legal documents that buyers are required to read and sign.</p><h3>Document Intelligence for Due Diligence</h3><p>The idea: build a tool that flags potential inconsistencies or omissions in legal documents like seller disclosures and property inspections. Not to replace professional advice, but to act as a second set of eyes.</p><p><strong>Minimum Valuable Product </strong>(market viability came later)</p><ul><li>Extract line items from PDF disclosures and inspection docs</li><li>Compare sections to surface contradictory or suspicious information</li><li>Use plain language prompts like:<br> <em>“Seller checked ‘No’ to water damage, but inspection noted ceiling stains in bedroom.”</em></li><li>Help users ask the right follow-up questions before signing a deal</li></ul><h3>Competitive Landscape: What Exists and What’s Missing</h3><p>There are plenty of tools that analyze the <em>numbers</em> behind real estate deals:</p><ul><li><strong>BiggerPockets</strong> and <strong>Roofstock</strong> offer rental calculators and ROI modeling.</li><li><strong>Redfin</strong> integrates climate and flood risk into property listings.</li><li><strong>Instabase</strong> offers powerful document processing, but it’s built for enterprises not individuals.</li></ul><p><strong>What’s missing?</strong><br> A lightweight, user-facing tool that analyzes the language and logic of disclosure documents. Something that supports buyers and new investors making one of the biggest decisions of their lives, not lenders or underwriting teams.</p><h3>Product Discovery</h3><p>This wasn’t just a product idea, it became a personal case study in product thinking. While I’ve taken projects from zero to one before, there’s something different about it when it’s your own idea and you don’t have design and engineering to validate assumptions with ‌real customers or prospects. It becomes easier to go down rabbit holes and get stuck.</p><h4>Discovery Defines the Problem</h4><p>First I wanted to understand the problem space fast and cheap. I scoured community forums, Reddit threads, and real estate complaint boards. While I did see some mentions of investors and users experiencing the same issues with inspection reports and seller disclosures, most people announced that it was a lesson learned and now they carefully evaluate those documents. What did stand out however, is that many real estate investors who rent vs. flip have the recurring issue with troubelsome tenants even when they use third party services to find and manage tenants.</p><h4>Urgency Creates Blind Spots</h4><p>Real estate is a high-stakes, fast-moving domain. That’s exactly where cognitive overload happens. Good tools step in when people are least able to think clearly. When we make decisions while stressed, we’re more likely to make mistakes because of the increase risk in cognitive bias <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC5146206/">https://pmc.ncbi.nlm.nih.gov/articles/PMC5146206/</a> and reduced cognitive ability due to physiological effects of stress <a href="https://www.waldenu.edu/online-masters-programs/ms-in-clinical-mental-health-counseling/resource/how-stress-impacts-decision-making">https://www.waldenu.edu/online-masters-programs/ms-in-clinical-mental-health-counseling/resource/how-stress-impacts-decision-making</a>.</p><h4>Rare Doesn’t Mean Low Impact</h4><p>Some risks are uncommon but expensive. Skipped permits, cracked foundations, or water damage might only affect a few buyers, but when they do, the consequences are severe and not everyone discloses properly and inspections don’t capture everything they should.</p><h3>Architecture</h3><p>Because I used to be a software developer, I couldn’t help but check out feasibility before market viability. In my experience working in product pods, this happens at the same time (divide and conquer), but since I was soloing it, my engineering brain took over and wanted to know IF and HOW we could build it. So, after discovery and defining the problem, I dove into what it would take to build the app.</p><h4>Painful Messy Data</h4><p>PropTech and HealthTech experience similar problems. Messy handwritten notes, forms, and other complicated PDFs with scanned checkboxes, blank lines, and vague “N/A” responses are difficult for machines to parse. OCR alone wasn’t enough. But using token proximity (like with word2vec) and building out related phrase clusters offered a simpler, explainable approach.</p><h4>Focus on Context, Not Just Content</h4><p>Line numbers alone are unreliable because some are blank or out of sync with content. Understanding context, like how a pest control date relates to a “No” checkbox for pest history requires inference beyond simple keyword detection. And this isn’t a problem you can simply throw an LLM at and hope for the best.</p><h4>Testing AI on Real Disclosure Forms</h4><p>As part of validating the technical feasibility of my idea, I experimented with using ChatGPT to detect inconsistencies in real seller disclosure documents specifically the Arizona SPDS form, which is structured but not machine-readable out of the box.</p><p>I uploaded one of my own seller disclosure PDFs and asked an AI workflow to identify red flags. A clear contradiction stood out: the seller checked <strong>“No”</strong> to knowing about any pest issues (Line 139), but just a few lines later (Line 142), checked <strong>“Yes”</strong> to having pest control treatment done and even listed the company and date.</p><p>Despite the inconsistency being obvious to a human (ok, obvious in hindsight), the AI didn’t flag it.</p><p>Why? The problem came down to document structure. Standard OCR tools struggled to accurately associate checkboxes and line numbers with their respective labels. And even once the text was extracted, large language models don’t inherently understand how questions across lines are semantically related unless those relationships are explicitly modeled.</p><p>This surfaced a critical insight: while AI is powerful, it still struggles with structured document nuance, especially when contradictions live in proximity but aren’t cross-referenced by design. Detecting this kind of issue would require either a fine-tuned model trained on many annotated examples (hard to do since there are no standardized forms) or a simpler prototype that uses <strong>proximity-based embeddings</strong> to detect semantic contradictions. Possibly something closer to word2vec or sentence transformer clusters, where terms like “pests,” “control,” and “No” could be plotted in a conceptual vector space and flagged when relationships don’t line up.</p><p>This experiment made it clear: without structured awareness or custom annotation, many red flags remain invisible to AI alone.</p><figure><img alt="semantic relationship between real estate disclosure form fields" src="https://cdn-images-1.medium.com/max/1024/1*zOC5NUrtQAgHbqa6b5vTxA.png" /><figcaption>Generated by ChatGPT</figcaption></figure><h4>Tools I Tested for Text Extraction and OCR</h4><p>As part of the technical analysis, I experimented with several tools to handle the core challenge: extracting structured data from messy, unstructured real estate documents. I tried <strong>Azure Document Intelligence Studio</strong>, which had promise but struggled with checkbox detection and bounding box accuracy on scanned PDFs. <strong>Google Vision API</strong> performed reasonably well for clean, typed documents but required custom logic to associate nearby text and line numbers. <strong>Amazon Textract</strong> offered more robust form parsing and checkbox recognition, but formatting issues were still frequent. I also explored open-source options like <strong>Tesseract</strong> (paired with Python and layout analysis scripts) and began experimenting with <strong>embedding-based clustering</strong> using sentence transformers to spot contradictions across sections. Each tool had trade-offs, and none could fully handle the complexity of disclosures and inspections without custom logic layered on top. So feasible, but not without a lot of engineering work!</p><p><em>Now, what about viability? Is there a market for this product?</em></p><h3>Why I Chose Not to Move Forward: Market Viability</h3><p>As promising as the concept was technically, I had to step back and look at the bigger picture, <strong>can this be a business?</strong> Here’s what I found:</p><h4>1. Data Access Is Limited and Fragmented</h4><p>The app depends on access to real estate disclosure forms and inspection reports, which are:</p><ul><li>Not standardized</li><li>Often handwritten or scanned</li><li>Protected by privacy laws and hard to access in bulk</li></ul><p>Without consistent data input, it’s difficult to scale or train a robust system that works across geographies and formats.</p><h4>2. The Problem Isn’t Top-of-Mind Year-Round</h4><p>This is a <strong>time-sensitive pain point</strong>. Most buyers only deal with these documents a few times in their lives and often learn the hard way. Once they’ve been burned, they’re more cautious, but the urgency disappears after the deal closes. Even for real estate investors who do more deals more often, they still believe that they won’t make the same mistake twice.</p><p>This means repeat usage and customer retention are low unless it’s bundled into a broader home-buying or investor tool.</p><h4>3. It’s a Feature, Not a Standalone Product</h4><p>The core value, flagging inconsistencies or red flags in documents, felt more like a <em>feature</em> than a standalone business. It would be incredibly valuable <strong>inside</strong> a platform like DocuSign, Redfin, or Roofstock… but less viable on its own without deep integrations or partnerships.</p><h4>4. The Willingness to Pay is Unclear</h4><p>Individual homebuyers may want peace of mind, but would they pay $20–50 for a one-time document scan? And would real estate professionals trust or recommend it when legal liability is at stake? These were questions I couldn’t answer confidently without more research or partnerships.</p><p><strong>Bottom Line</strong>: While the problem is real and the pain is tangible, the market conditions, usage patterns, and monetization model didn’t support building it out, at least not as a solo, standalone product.</p><p>And that’s okay. Product thinking means knowing when to move forward and when to pivot your energy elsewhere.</p><h3>The Bigger Picture</h3><p>This project reminded me why I love product discovery. Not every side project needs to become a feature, product, or startup, but exploring this space helped sharpen how I think about:</p><h3>Product Thinking Takeaways</h3><ul><li><strong>Architecting for Good, Better, Best and at What Cost?</strong><br> Not every feature needs to be “best in class” if “good enough” delivers the core value. I explored several implementation paths from simple heuristics to embedding models to full-on fine-tuned LLMs and realized that each jump in sophistication comes with real tradeoffs in cost, accuracy, and speed to value. A thoughtful architecture weighs user trust, technical complexity, and opportunity cost. In uncertain markets, simplicity often wins.</li><li><strong>Decision-Making Is Multifaceted and Rarely Rational</strong><br> Whether it’s a buyer rushing to close a deal or a product team greenlighting a feature, decisions are driven by far more than logic. Emotions like fear of missing out, urgency, and post-purchase regret shape behavior. Products must be designed with these invisible forces in mind not just to inform, but to reassure, warn, or slow users down when necessary.</li><li><strong>Products Sitting in Changing, Challenging Markets Are High-Risk Ventures</strong><br> Timing, regulation, market sentiment, and economic volatility all play outsized roles when you’re building in a space like real estate or AI. A product might be solving a real problem, but if conditions don’t support adoption or the problem isn’t urgent right now, even great products can fail. Navigating this means stress-testing not just your product idea, but your assumptions about timing, buyer behavior, and market entry strategy.</li></ul><p>Thanks for reading through my journey, where in October of 2024, I (almost) became a founder.</p><p><strong>If you’re building anything in the risk assessment, document intelligence, or prop-tech space, I’d love to connect.</strong> And if you’re just someone who’s been burned by a bad disclosure, I see you.</p><h3>About Me</h3><p>If you’re hiring and looking for someone who thinks like a researcher, builds like an engineer, and connects the dots between users and business goals, let’s talk. I’ve worked in tech for 12+ years across product, marketing, and engineering roles always advocating for the customer. I care about solving real problems, asking the right questions, and making things that work for people. Let’s connect on <a href="https://www.linkedin.com/in/stephanielkim/">LinkedIn</a> and check out some of my experiments using AI for automation on <a href="https://github.com/stevielkim?tab=repositories">GitHub</a>.</p><p><em>Written by a tired human, edited and formatted with ChatGPT and Writer</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26951aa86096" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First Five Minutes: Finding the Hook in Reddit’s Onboarding Flow]]></title>
            <link>https://medium.com/@StevieLKim/the-first-five-minutes-finding-the-hook-in-reddits-onboarding-flow-47ce6340eebb?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/47ce6340eebb</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Tue, 10 Jun 2025 15:38:00 GMT</pubDate>
            <atom:updated>2025-06-10T16:00:09.955Z</atom:updated>
            <content:encoded><![CDATA[<p>How optimized onboarding flows create confident long-term users who become champions of your product!</p><figure><img alt="Reddit’s onboarding flow with happy users" src="https://cdn-images-1.medium.com/max/1024/1*uNQS_De9oUESgVvGy51izg.png" /><figcaption>Image generated by ChatGPT</figcaption></figure><p>First impressions shape everything. For digital products, those first few minutes can determine whether a user becomes engaged or quietly disappears. I’ve spent much of my career thinking about those moments and how to reduce friction, spark motivation, and guide people toward value before they drop-off. So when I decided to examine Reddit’s onboarding, I wasn’t just curious about usability. I wanted to understand how well Reddit helps new users find their footing and discover why the platform is worth sticking around for.</p><p>This post is part UX research summary, part product onboarding critique, and part user story. If you’re a product manager, designer, or researcher working on activation and onboarding, I hope this post reminds you that everyone is a new user at some point, and you’ve probably forgotten what that feels like. So get out there, talk to your new users, find the ones that have bounced (you should have their contact details), and ask new employees for their hot take on your onboarding experience. Because while the numbers can tell you what’s happening, they can’t tell you why.</p><h3>Reddit at a Glance</h3><p>Reddit is a discussion-based social platform centered on user-generated content and interest-based communities called “subreddits” ranging from plant care to AI ethics to wolves eating watermelons (<a href="https://www.reddit.com/r/WolvesWithWatermelons">r/WolvesWithWatermelons</a>).</p><ul><li><strong>Founded:</strong> 2005</li><li><strong>Users:</strong> 108+ million daily active users (as of Q1 2025)</li><li><strong>Product Domain:</strong> User-generated content, interest-based communities</li><li><strong>Revenue Model:</strong> Primarily ad-based with Reddit Premium and data licensing (e.g., Google, OpenAI)</li><li><strong>Recent Growth:</strong> $392.4M in Q1 2025 revenue (+61% YoY)</li><li><strong>Mission:</strong> To empower communities through open dialogue and accessibility of knowledge</li></ul><h3>Reddit’s Value Proposition</h3><p>Reddit’s impressive growth comes from its uniqueness and authenticity. It’s not built around influencers or algorithmic popularity. Its value comes from users sharing knowledge, humor, advice, and curiosity in highly specific communities. But that strength can also be a weakness, because if Reddit doesn’t help people find their community quickly, they’ll leave without ever seeing what makes the platform special. The onboarding experience must help users find <em>their people</em>, not <em>the most popular people</em>.</p><p>Reddit is structurally closer to Discord, which also rewards sustained community engagement over reach. However, Reddit’s asynchronous format, public posting, and upvote/downvote system demand early clarity and alignment.</p><p>As Reddit Answers (beta) puts it:</p><blockquote>“Reddit offers a vast array of communities and discussions. Its upvote/downvote system curates relevance. Anonymity fosters honest conversations. Users come for both casual browsing and deep dives.”</blockquote><h3>Why Reddit’s Free Users Are Core to Growth</h3><p>Free users don’t pay directly, but their activity powers Reddit’s business:</p><ul><li><strong>Advertising:</strong> Engagement generates targeting signals for ad buyers</li><li><strong>Content Creation:</strong> Active users contribute to the conversations that make Reddit worth visiting</li><li><strong>Search Engine Traffic:</strong> Content is indexed and drives top-of-funnel visibility</li><li><strong>Perceived Activity:</strong> Lively communities enhance credibility for new users (via herd behavior and social proof)</li></ul><p>These free users are the foundation of Reddit’s ecosystem and revenue model. While they do not pay directly, their engagement is what fuels the platform’s primary revenue streams: advertising and data licensing. Advertisers pay to access Reddit’s diverse, highly engaged communities, and targeting depends on active participation and meaningful interest signals from these users. Free users also serve as social proof. The presence of active discussions, visible upvotes, and high engagement cues new users that the platform is trustworthy and active which serves as an example of herd behavior and perceived credibility via group consensus.</p><p>The richer the behavior data from free users such as what subreddits they join, what posts they upvote, and how long they spend on different content, the more effectively Reddit can personalize experiences and sell targeted ad inventory. Additionally, active users create the content and conversations that make Reddit valuable to everyone else, including paying customers and lurkers who discover Reddit via search engines.</p><p>Improving onboarding for free users is not just about retention. It is about sustaining the health of the entire ecosystem that Reddit’s business model depends on.</p><h3>My User-Testing Approach</h3><p>This case study focuses on free users, who make up the majority of Reddit’s audience. I walked through Reddit’s onboarding from sign-up to first engagement, focusing on three things:</p><ul><li>Mapping the journey from account creation to the home feed</li><li>Identifying core success signals such as subreddit joins, upvotes, and comments</li><li>Surfacing friction points that might derail momentum</li></ul><p>Many users experience Reddit first through search results. By the time they officially onboard, they may already associate the platform with value. The question is whether Reddit reinforces that initial value or allows it to fade.</p><h3>Customer Journey &amp; UX Analysis</h3><p>Though I’ve used Reddit since 2012, I created a fresh account to simulate a true first-time experience. Here’s what stood out:</p><p><strong>1. Sign-up Confusion</strong></p><ul><li>Reddit doesn’t indicate if you’ve used an email before. I had to try a few</li><li>Since most people juggle multiple emails (28% have four or more), this creates unnecessary friction and increases the risk of drop-off</li></ul><p><strong>2. Overwhelming Interest Selection</strong></p><ul><li>The small modal felt like a doomscroll with no way to expand or prioritize. This flood of options can contribute to decision fatigue which is a cognitive state where the brain becomes less effective at making decisions after being overwhelmed by too many choices</li><li>My actual interests didn’t appear early, so I selected something random since you have to choose at least one interest to continue</li><li>According to the Zeigarnik Effect, I’ll remember this unfinished task more vividly, and negatively</li><li>Familiarity promotes comfort. Novelty drives dopamine. This experience provided neither</li></ul><p><strong>3. Homepage Felt Flat</strong></p><ul><li>The layout wasn’t overwhelming, but the content felt irrelevant</li><li>Because I skipped interest selection, I landed in a generic feed</li><li>I clicked into “Explore Communities,” which was more structured and useful</li></ul><p><strong>4. Exploration Helped</strong></p><ul><li>Around minute six, I searched for “cognitive psychology” and found little engagement</li><li>I then searched for “agentic AI” and found higher engagement</li><li>A minor annoyance: if I scrolled down, then decided to join a subreddit, I had to scroll back up to do it. This may be intentional to invoke FOMO or loss aversion</li></ul><p><strong>5. The Aha Moment (Mine, Not Theirs)</strong></p><ul><li>I replied to a post around minute eleven but felt no emotional reward</li><li>The next day, I received a reply. That moment made the platform click for me</li></ul><p><strong>6. Later Use</strong></p><ul><li>Explored Reddit Answers which is in beta. Helpful in helping users orient themselves to Reddit’s terminology and concepts such as Karma, upvoting/downvoting, etc.</li></ul><p><strong>Key Insight:</strong> Reddit’s assumed Aha moment may be “joining a subreddit,” but mine came from interaction with the community in the form of dialogue in the comments. Effective onboarding must support both personalization and connection.</p><p>Check out my onboarding experience on <a href="https://www.loom.com/share/ee5fa70c478641b4ae8de67caaf5c9ac?sid=e3cd69de-2783-4e89-8e4e-62b9ebb9258e">Loom</a> where I captured the initial onboarding experience and a later <a href="https://www.loom.com/share/243509a273734c7384dc04b29d5e1376?sid=8207b1ea-0702-4fdc-80f0-42eb5e6df8f7">video </a>when I felt the value of the platform 22 hours later.</p><h3>User Research: Reddit Answers</h3><p>To explore other people’s experiences and compare them with my own, I used Reddit Answers to gather AI-generated summaries of user sentiment. The most common complaints included:</p><p>Reddit’s own AI summarization tool reveals consistent complaints:</p><ul><li><strong>Lack of Guidance:</strong> “I don’t know where to start”</li><li><strong>Information Overload:</strong> Too many concepts too soon without orientation (karma, posting rules) are overwhelming and confusing</li><li><strong>Subreddit Etiquette Anxiety:</strong> Fear of downvotes or bans due to unique norms for each community</li><li><strong>Mobile Frustrations:</strong> Navigation and bugs</li></ul><p><strong>What Users Want:</strong></p><ul><li>Clear, step-by-step onboarding</li><li>Better subreddit discovery tools</li><li>More visible and understandable community guidelines</li><li>A smoother, more intuitive mobile experience</li></ul><p><strong>Validation:<br></strong>My experience mirrors what users describe. The biggest gaps are not technical but psychological. Reddit fails to help new users:</p><ul><li>Understand the platform</li><li>Discover relevant communities</li><li>Feel confident participating</li></ul><p>UI improvements are valuable, but orientation, safety, and momentum are what truly shape retention.</p><h3>UX Recommendations to Improve Reddit Onboarding</h3><p><strong>Guide Users with Purpose</strong></p><ul><li>Use visual progress indicators and onboarding micro-goals</li><li>Frame onboarding as a guided journey rather than a checklist</li></ul><p><strong>Make Discovery More Meaningful</strong></p><ul><li>Expand interest filters, including niche and trending topics</li><li>Allow for expansion of the interest modal so it doesn’t feel so overwhelming</li><li>Set minimum interest selection to three instead of one to populate home feed</li><li>Offer personas such as “I’m here for…”</li></ul><p><strong>Enable Early Social Interaction</strong></p><ul><li>Suggest welcoming, high-response threads for new users</li><li>Promote low-friction starter communities</li></ul><p><strong>Reduce Cognitive Overload</strong></p><ul><li>Use progressive disclosure</li><li>Introduce features (karma, rules) only when relevant</li><li>Use tooltips and just-in-time education</li></ul><p>By breaking onboarding into bite-sized steps, we’re supporting the brain’s natural preference for chunking, meaning, we’re grouping related information to reduce cognitive load and enhance retention. Through just-in-time guidance, we can respect working memory limits by delivering information only when it’s relevant, reducing overload and improving retention.</p><p><strong>Fix Mobile Frustrations</strong></p><ul><li>Improve the navigation structure</li><li>Introduce lightweight animations or tooltips for key actions</li><li>Enhance overall app performance</li></ul><p><strong>Reinforce and Re-engage</strong></p><ul><li>Resume onboarding in future sessions</li><li>Highlight skipped steps with helpful prompts</li></ul><p><strong>Optimize for SEO and AI Entry Points</strong></p><ul><li>Tailor onboarding if user arrives from content via search</li><li>Present contextual overlays tied to content topic</li><li>Let users onboard without leaving the post they landed on</li></ul><h3>Intuitive Onboarding: A Step-by-Step Framework</h3><p>To make Reddit’s onboarding process more intuitive and less overwhelming, it helps to structure it in small, digestible stages that align with user goals.</p><p>Here’s how Reddit could break it down:</p><p><strong>Clarify Intent Early</strong></p><p>Personalize and set expectations with a prompt: <em>“I’m here to… Explore hobbies / Ask for advice / Follow news”</em></p><p><strong>Simplify Sign-Up</strong></p><p>Save previously used email and display what’s next</p><p><strong>Show Micro-Steps</strong></p><p>Progress indicators or checklists <em>“Step 1 of 3: Find communities you like”</em></p><p><strong>Teach in Context</strong></p><p>In-feed tooltips <em>“Click the upvote if this is helpful and you want to add to this users karma”</em> or <em>“Join a community to customize your feed”</em> or “<em>comment or post something helpful or interesting to gain karma.”</em></p><p><strong>Just-in-Time Education</strong></p><p>Feature introductions only when relevant</p><p><strong>Reinforce Progress</strong></p><p>Use animations or milestone confirmations: <em>“Nice! You joined your first community.”</em> and a visible progress bar.</p><p>Provide feedback loops: <em>“Users who joined 3+ communities usually stick around longer. Want to keep going?”</em></p><p><strong>Continue Onboarding Later</strong></p><p>Resume flow in future sessions, guided by behavior</p><p>These approaches are grounded in user-centric design principles and are proven to reduce friction while improving time-to-value. They turn onboarding into a sequence of quick wins, which helps users feel confident, oriented, and motivated to return.</p><p>Note: some of these best practices might be already in use, but don’t appear within the time frame that I recorded my experience.</p><h3>Final Thoughts</h3><p>Reddit’s onboarding does many things right, it’s fast and easy to start, but it often fails to guide users toward what truly matters: discovering community, understanding platform culture, and feeling confident enough to engage.</p><p>The platform’s long-term growth depends on getting this right. Free users power Reddit’s ecosystem, and without helping them reach their “aha moment,” the product’s core value remains hidden.</p><p>Effective onboarding isn’t just about understanding how many users complete your onboarding steps. It’s about building trust and showcasing value throughout the experience.</p><blockquote>Don’t just ask “Did they finish our onboarding flow?”</blockquote><blockquote>Include: “Did they discover?” “Did they engage?” “Did they return?”</blockquote><p>If this post helped you rethink onboarding:</p><ul><li>Share it with your product or UX team</li><li>Map your own onboarding and flag friction points</li><li>Connect with me to trade notes or brainstorm together</li></ul><h4>About Me</h4><p>If you’re hiring and looking for someone who thinks like a researcher, builds like an engineer, and connects the dots between users and business goals, let’s talk. I’ve worked in tech for 12+ years across product, marketing, and engineering roles always advocating for the customer. I care about solving real problems, asking the right questions, and making things that work for people. Let’s connect on <a href="https://www.linkedin.com/in/stephanielkim/">LinkedIn</a> and check out some of my experiments using AI for automation on <a href="https://github.com/stevielkim?tab=repositories">GitHub</a>.</p><p><em>Written by a tired human, edited and formatted with ChatGPT and Writer</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47ce6340eebb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating SEO Medium Posts with CrewAI Agentic Workflows]]></title>
            <link>https://medium.com/@StevieLKim/automating-seo-with-crewai-3e34407226c1?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e34407226c1</guid>
            <category><![CDATA[agentic-workflow]]></category>
            <category><![CDATA[v0]]></category>
            <category><![CDATA[crew-ai]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 18:01:26 GMT</pubDate>
            <atom:updated>2025-06-27T21:28:35.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="AI image of a man eating chocolate" src="https://cdn-images-1.medium.com/max/1024/1*gwD4JQQAhxrmBEOG0EHssg.png" /><figcaption>AI Should Allow For More Pool Time And Eating BonBons</figcaption></figure><p>Let’s face it, we’re forgetful and lazy creatures who would rather lounge by the pool eating bonbons than spend our valuable time doing inane activities such as updating old blog posts to improve SEO. Sure, I was familiar with optimizing for SEO during my time as a developer advocate, but when I started writing on my personal blog during my sabbatical, I just wanted to get something out the door without worrying about visibility. However, whenever I thought about going through each blog post to analyze and edit, I wondered, how bad could it be? After all, I have bonbons to eat.</p><p>So I ran my blog through a free SEO tool. As expected, it flagged several issues. Many were outside my control (thanks, Medium), but I could still update headers, inject better keywords, and add descriptive metadata.</p><p>But I didn’t want to:</p><ul><li>Manually reread every post</li><li>Get lost in five open tabs of SEO best practices</li><li>Rewrite content that was already decent</li><li>Painstakingly brainstorm better titles or headers</li></ul><p>In short, I wanted to preserve the intent and value of each post, make them easier to find, and avoid wasting mental energy thinking about SEO.</p><p>So I asked myself, what if I built a system that could read, analyze, and suggest improvements to this lazy, bonbon-eating human?</p><h3>Automate What Drains You, Do What Fuels You</h3><p>A few months ago, I experimented with<a href="https://docs.crewai.com/"> CrewAI</a>, a flexible agent-based framework that I wrote about in a <a href="https://medium.com/@StevieLKim/crewai-and-me-part-2-ab63cdc755b1">previous post</a>. This time, I wanted to dive deeper into the tooling and delegate the tedious task of SEO optimization to agents.</p><p>Sure, I could have copied each blog post into ChatGPT and asked it to optimize the content, or written a Python script using<a href="https://www.selenium.dev/"> Selenium</a>,<a href="https://scrapy.org/"> Scrapy</a>, and <a href="https://openai.com/index/openai-api/">OpenAI’s API</a>. It would’ve been faster (I know from previous experience). But where’s the fun in that?</p><p>Here’s the gist: I wanted to boost my Medium posts’ on-page rankings on search engine results pages (SERPs) by adding relevant keywords to titles and headers, and by including metadata like alt text and meta descriptions. Medium’s formatting limitations ruled out some types of improvements, but with the rise of AI in search (like Google’s AI Overviews), optimizing for clarity and relevance is more important than ever. My goal: enhance searchability without rewriting posts from scratch or losing my voice.</p><h3>The CrewAI Pipeline</h3><p>I built a workflow using CrewAI agents that could:</p><ol><li>Scrape my blog content</li><li>Analyze it for SEO improvements and AI summary inclusions</li><li>Generate revised versions</li><li>Evaluate the changes</li><li>(Optional) Upload the post back to Medium</li></ol><p>Spoiler: that last step was not the right priority. More on that later.</p><h3>Stuck in the Void of System Architecture</h3><p>CrewAI gave me a lot of flexibility. Maybe too much for a curious mind like mine.</p><p>Naturally, I fell into a rabbit hole of experimentation:</p><ul><li>Should agents operate sequentially, or in a hierarchy?</li><li>Should I keep tweaking prompts or try multiple crews or flows?</li><li>Should I write a custom tool for basic parsing of a directory?</li><li>What’s the best agent-to-task ratio?</li><li>Is collaboration even working? How do I check?</li><li>Should I use async tasks? (Sidebar: One startup I worked at had a sign in the kitchen that said “You must be this tall to write concurrent code.” Am I disqualified for not even being 5&#39;4&quot;?)</li><li>Do I really need to automate uploads, or is that just shiny object syndrome?</li></ul><p>To move forward, I realized I needed to step back and evaluate:</p><ul><li><strong>Define the highest-leverage outcome</strong>: Edited optimized drafts I could manually upload.</li><li><strong>Defer the lowest-value step: </strong>Automating uploads wasn’t urgent. Ideation and editing were highest-priority.</li><li><strong>Prototype over polish</strong>: Just get the crew working and outputs flowing before trying to optimize every little thing.</li></ul><h3>CrewAI Architecture</h3><p><strong>The Agents:</strong></p><ul><li><strong>Scraper Agent:</strong> Pulls original blog posts saved locally</li><li><strong>Researcher Agent:</strong> Evaluates structure, headers, keywords</li><li><strong>Reporting Analyst Agent:</strong> Generates optimized versions in markdown</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qEft413f3XONE-qV" /></figure><h3>Small Wins Using Agentic AI</h3><ul><li><strong>Task-first design </strong>helped me define jobs first, then assign them to agents.</li><li><strong>Breaking up tasks</strong> into smaller subtasks produced more consistent results</li><li><strong>Reviewing agent reasoning</strong> helped debug issues, I manually saved mine to a file, but next time I’ll capture logs using callbacks (<a href="https://github.com/crewAIInc/crewAI/issues/833">CrewAI Issue #833</a>)</li></ul><h3>Challenges With AI Frameworks</h3><ul><li><strong>Agent Roles and Backstories </strong>were unhelpful, CrewAI’s docs suggest giving Tasks over Agents an 80% vs 20% of your time and effort.</li><li><strong>LLM variability</strong> made output unpredictable. I plan to reset memory per agent next time to isolate changes (<a href="https://community.crewai.com/t/long-term-memory/126/2">discussion thread</a>)</li><li><strong>File handling</strong> was shockingly fragile. A basic read/write task was where the most bugs happened. Adding read/write tools wasn’t enough, agents needed code execution permission otherwise the task got kicked to an agent that did have access.</li><li><strong>The hierarchical process</strong> didn’t work as expected. I wanted to run Scraper and Researcher tasks in parallel. Unfortunately, the default manager kicked off the Reporting Agent before the others finished and I couldn’t get a custom agent working. Next time I’ll try flows and multiple crews.</li><li><strong>I wanted to automate</strong> the Medium log-in process, mostly because I wanted an excuse to write a custom tool. I got it to work logging in via Facebook SSO using trusty Selenium, but since the agents couldn’t rewrite the entire blog post for me (possibly due to memory constraints or unclear prompts) I ditched the effort.</li></ul><h3>Mixed Results via Automation</h3><p>Some previous iterations got me subjectively better outcomes, but here were suggestions for one of my old blog posts:</p><pre>### Suggestions for &#39;Real Estate Investing: Protect Your ROI By Planning Ahead&#39;<br><br>1. **Title Suggestions:**<br>   - &#39;Strategic Real Estate Investing: Safeguarding Your ROI&#39;<br>   - &#39;Real Estate Investment: Proactive Planning for Maximum ROI&#39;<br>   - &#39;ROI Protection in Real Estate: The Power of Planning Ahead&#39;<br><br>2. **Header Modifications:**<br>   - Use H2 headers for sections like &#39;Introduction&#39;, &#39;Investment Strategies&#39;, &#39;Risk Management&#39;, and &#39;Conclusion&#39;.<br>   - Add subheaders (H3) for detailed points under each major section.<br><br>3. **Keyword Suggestions:**<br>   - Incorporate keywords such as &#39;real estate strategies&#39;, &#39;investment planning&#39;, and &#39;ROI protection&#39; in the content.</pre><p>With the agent’s final selection in html:</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>&lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;<br>    &lt;title&gt;Strategic Real Estate Investing: Safeguarding Your ROI&lt;/title&gt;<br>    &lt;meta name=&quot;description&quot; content=&quot;Learn how proactive planning can maximize your ROI in real estate investing.&quot;&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>    &lt;h1&gt;Strategic Real Estate Investing: Safeguarding Your ROI&lt;/h1&gt;<br>    &lt;h2&gt;Introduction&lt;/h2&gt;<br>    &lt;p&gt;Real estate strategies are essential for successful investments...&lt;/p&gt;<br>    &lt;h2&gt;Investment Strategies&lt;/h2&gt;<br>    &lt;h3&gt;Understanding Market Trends&lt;/h3&gt;<br>    &lt;p&gt;Investment planning is crucial for identifying opportunities...&lt;/p&gt;<br>    &lt;h2&gt;Risk Management&lt;/h2&gt;<br>    &lt;h3&gt;Mitigating Potential Losses&lt;/h3&gt;<br>    &lt;p&gt;ROI protection involves assessing risks and implementing strategies...&lt;/p&gt;<br>    &lt;h2&gt;Conclusion&lt;/h2&gt;<br>    &lt;p&gt;In conclusion, proactive planning is key to safeguarding your ROI...&lt;/p&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>Check out the rest of my results <a href="https://github.com/stevielkim/Seo-Agents">on GitHub</a>. Note: I only ran the crew for three blog posts to keep it brief.</p><h3>SEO Updates Using CrewAI and V0</h3><p>On a whim I tried <a href="https://v0.dev/">V0</a> by Vercel, gave it a few prompts, told it to go test itself (in my defense it kept writing code that failed), and it returned similar results in under an hour.</p><p>That’s where we are now, you spend days learning one tool, only to find another that does it faster, easier, and with zero expertise.</p><p>All of this for SEO updates I could have done manually in less time, but naming things is hard, so I let an LLM do it for me. But will I take the time now to manually update the suggested changes? Blah. Bonbons are waiting.</p><p>Still, I don’t regret it. I learned more about CrewAI and agent design than I would have from a tutorial. And hey, next time I need to generate content, maybe I’ll just pick something fun to build and let my Sol Arbiter data spike handle the rest without me lifting a finger, if you know, you know (and are into <a href="https://jnchaney.com/series/sol-arbiter/">Cyberpunk</a> like me).</p><p><em>Written by a tired, but caffeinated human. Editing and formatting by ChatGPT.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e34407226c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Design Case Studies: Evaluating the Necessity of GenAI in Everyday Life]]></title>
            <link>https://medium.com/@StevieLKim/ai-everywhere-just-because-we-can-doesnt-mean-we-should-f77b070c499f?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77b070c499f</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Fri, 03 Jan 2025 02:09:46 GMT</pubDate>
            <atom:updated>2025-05-02T02:24:11.302Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Stock price is down? Add a chatbot! Board on your back? Throw in a copilot!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uAWdR5fSCJoB40dFDqqYPA.jpeg" /><figcaption>My preferred CoPilot via <a href="https://www.freepik.com/author/catalyststuff">FreePik</a></figcaption></figure><p>Over the past year we’ve seen some pretty horrible examples of generative model-based features and products. While features that utilize GPTs (generative pre-trained transformers) have the potential to transform user experiences and drive significant ROI, it’s not the answer to every product team’s objectives. As with any innovation, AI should solve a real user problem or help users achieve their goals. Most AI features have so far been the result of FOMO and are half-baked solutions shoehorned into products without clear intent or thoughtful design. This can lead to features that fail to solve real user problems or worse, create new ones.</p><p>In this post, I’ll explore how AI can be thoughtfully implemented to enhance user experiences. I’ll use real-world examples, such as CrewAI’s copilot search functionality, Pinterest’s feed flooded with AI-generated images, and MasterClass’s Teaching Assistant, to examine what works and what doesn’t. At the end of the day, AI should be innocuous, helpful, and seamlessly integrated into the user’s workflow, not make us rage quit an application.</p><h3>Working Backwards with Intentional AI Design</h3><p>AI powered or not, every initiative should begin with the end in mind. What is the business trying to achieve right now? What about in 1–3 years? How about in 5–10? Depending on the maturity of the organization you might not have those answers at your fingertips, but you should know your company’s mission and vision for the future. Starting with the end in mind orients everyone to the same coordinates quickly. Then you can move onto how to make that magic happen with product discovery and user testing.</p><ul><li><strong>Business Justification:</strong> What is the most important thing to get right for the business right now? Is it innovation to gain market share? Efficient operations to trim costs? Or is it quality control to decrease customer churn? You need to understand the state and goals of the business before diving into the latest diffusion models so your app can have AI generated images of porcupines.</li><li><strong>Product Discovery</strong>: Is there a genuine problem that needs solving? How many users who belong to your ideal customer profile segment experience this issue? How are they solving it now or do they not have a solution? Why should you solve it? How are your competitors solving this problem or are they? What would happen if you didn’t solve this or at least not right now? These are just some of the questions you and your team need to answer before googling “chatbot vs copilot”.</li><li><strong>Value Creation</strong>: Does the feature create value by enhancing the experience, removing barriers, or enabling users to achieve their goals more efficiently? Does it cost more to build than the value it provides? How can you measure the value and the cost to build it?</li><li><strong>Value Delivery &amp; User Testing</strong>: Test your hypothesis! Does it solve the problem you anticipated it would? How do users interact with the feature? Does it work as intended? Does it get used at all? Does it make people cry with joy or out of frustration? The solution should always outweigh any drawbacks. While these potential drawbacks should be anticipated ahead of time during product discovery and solution ideation, users sometimes act in mysterious ways. Therefore, it’s important to roll out testing to a small group of trusted users first.</li></ul><p>Starting with the end goal in mind impacts the amount of time, money, and effort you and your team can allocate to user problems and goals. It’s impossible to do everything, so by focusing on what truly benefits both the business and the users, we might just gain some loyal (and hopefully loud) customers who champion our product.</p><h3>AI UX Design Case Studies: The Good, Bad, And Ugly</h3><h4><strong>The Good: CrewAI’s Enhanced Search</strong></h4><p>Recently, I wrote a couple of <a href="https://medium.com/@StevieLKim/crewai-and-me-part-2-ab63cdc755b1">blog posts</a> regaling my experience using <a href="https://www.crewai.com/open-source">CrewAI’s open source</a> multi-agent library to create compelling short-term real estate investment reports. While the generated reports were less than ideal, I still walked away with an appreciation for what CrewAI is trying to accomplish by making agentic workflows easy to use and understand. They’ve put a lot of thought into their onboarding process including the documentation and getting started guide but what really stood out to me was the co-pilot functionality embedded in their search bar. If any of you have Instagram you know how <a href="https://www.nngroup.com/articles/ai-user-value/">bad an experience</a> can be when you mess with search.</p><p>Instead of getting in the way of a user’s ability to get a thing done, CrewAI provides a list of options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DD_WgUWQ73hFCsAp" /></figure><p>Notice the first option available is to explain the search query using AI and then normal search results are listed. The CrewAI folks aren’t assuming they know what information you need, so they provide options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mtMmQ14H2w6J60Ox" /></figure><p>If AI is selected, it’s actually helpful, but as always double check the results because like any generative model, the results can make sense, but not be factually true.</p><p>The reason I found this functionality so helpful is that we often focus on completing our tasks and learning just enough to finish them, especially when facing a deadline. But, by offering up meaningful context that I wouldn’t have unless I read the docs front and back, I got to learn the what and the why behind my query.</p><p>In short, by providing rich, contextual answers to queries, this AI feature enhanced my user experience without interrupting my workflow.</p><ul><li><strong>Innocuous</strong>: Users get the information they need quickly and efficiently without blocking them from doing their thing.</li><li><strong>Helpful</strong>: The AI improves the value of the documentation by answering not only the “what” but also the “why.”</li><li><strong>Seamless</strong>: The feature integrates naturally into the existing product.</li></ul><h4><strong>The Ugly: AI-Generated Images Taking Over Pinterest</strong></h4><p>I admit that I hadn’t been on Pinterest for longer than I can remember, so I’m not sure how long this has been going on, but I was doing some landscape planning over the colder months and wanted some inspiration. What I saw in my feed was cringey at best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PVURImgxhYlSdVwA" /></figure><p>Even though Pinterest itself isn’t generating AI images in users feeds, they appear everywhere and while some users are taking it in stride, others want AI generated content gone. You can see both sides taking to the debate in this<a href="https://www.threads.net/@pearlmania500/post/C62g4syN59-"> Instagram thread</a>.</p><p>While these images aren’t harmful, they often look overly “perfect,” making them feel fake and unattainable. Users <a href="https://www.socialmediatoday.com/news/survey-finds-consumers-crave-authenticity-and-user-generated-content-deli/511360/">crave authenticity</a> on social media and from the <a href="https://www.linkedin.com/pulse/why-consumers-crave-authenticity-lessons-small-brands-rebelsmarket-u45xf/">companies they interact with</a> and when ‌content feels disconnected from their reality, it undermines trust and engagement.</p><p>Pinterest’s mission (according to their <a href="https://www.pinterestcareers.com/our-life/">Careers page</a>) is, “…to bring everyone the inspiration to create a life they love,” and “Every single person should be able to search, save and shop the best ideas in the world for all of life’s moments.”</p><p>But if users aren’t inspired by AI generated images, then maybe the company can do more to help users manage their feeds. Right now, users can report a pin to remove it, but there isn’t an option to remove it due to it being an AI image, although they can hide it because it’s blurry or “other”. This is what I did to discourage the algorithm from showing me AI content in my feed and query results, but putting that burden onto your user isn’t the best design practice. And, if Pinterest wants to increase revenue through ads, they probably should figure out which ones turn users off.</p><p><strong>Key insights:</strong></p><ul><li><strong>Authenticity Drives Connection</strong>: Users want to see achievable, relatable solutions by people and brands they can trust.</li><li><strong>Don’t Underestimate Aesthetics:</strong> When aesthetics are a key selling point of your brand, don’t undermine that quality by allowing images that detract from the product’s visual appeal.</li><li><strong>Enable Choice:</strong> Help your users manage the content they see and interact with.</li></ul><h4><strong>The Bad: MasterClass’s AI Teaching Assistant</strong></h4><p>Chatbots are a jack-in-the-box surprise we never wanted. There’s nothing worse than navigating to a website or in this case, a MasterClass course and getting interrupted by a chatbot asking inane questions before you even press play on the first video. I’m fairly certain that no user has ever asked for a chatbot. They might have asked for a way to find the information they needed in a specific video, especially if they’ve already gone through it before and wanted to reference something. But isn’t that what My Notes feature is for? Or maybe a user asked for a more interactive experience since ‌courses consist of passively watching someone lecture on a topic of interest. Who knows, the point is that this chatbot isn’t the TA I want or need and while yes, you can hide it for the current video, it’ll pop back open for the next one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zmLNnoRdVX3OpjvH" /></figure><p>Here’s what could improve it:</p><ul><li><strong>Opt-In Not Out</strong>: Allow users to summon the TA when they need it, for instance if they didn’t understand the content or wanted feedback on a problem they are having related to putting the learnings to work in real life.</li><li><strong>Focus on Learning Retention</strong>: Offer features like note-taking assistance or interactive conversations after each video completes about that specific video.</li><li><strong>Personalization: </strong>Offer recommendations for further learnings from other courses that relate to what the student took notes on or bookmarked.</li></ul><h4>Designing for Seamless AI Integration</h4><p><strong>Innocuous</strong>: AI features should enhance the user experience without being intrusive when added to an established product.</p><p><strong>Helpful</strong>: The feature must provide tangible value. Whether it’s saving time, reducing frustration, or adding convenience, the benefit should be clear.</p><p><strong>Authentic</strong>: Users can tell when an experience feels genuine versus artificially forced. AI should foster connection and relatability.</p><h4>We’re Still in Charge of Product Design and Development</h4><p>AI has the power to transform user experiences, but only when implemented thoughtfully. Just like anything we build we should ask ourselves:</p><ul><li>Does it solve a real user problem?</li><li>Does the problem or opportunity align with our business goals?</li><li>Does the solution enhance the experience without creating new frustrations?</li><li>Is it authentic, helpful, and seamlessly integrated?</li></ul><p>By focusing on these and other product design and development principles, we can ensure that our AI features deliver real value.</p><p>I’d love to hear your thoughts: How have you approached AI integration in your own products? What lessons have you learned along the way?</p><p>Let’s continue the conversation. Or not, because I won’t make you like some chatbots I know.</p><p><em>If you’re hiring for product-related or GTM roles, I’d love to connect and discuss how I could contribute to your team!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77b070c499f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real Estate Investing: Protect Your ROI By Planning Ahead]]></title>
            <link>https://medium.com/@StevieLKim/real-estate-investing-protect-your-roi-by-planning-ahead-5a5473add8fc?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a5473add8fc</guid>
            <category><![CDATA[real-estate-investments]]></category>
            <category><![CDATA[real-estate]]></category>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[real-estate-market]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Mon, 30 Dec 2024 00:14:25 GMT</pubDate>
            <atom:updated>2024-12-30T00:14:25.742Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8nVG1iJNo4llmZTM9WFo8w.png" /><figcaption>ChatGPT’s take on my title</figcaption></figure><p>Whether you’re looking for your dream home, are a budding investor looking to make money moves, or are a seasoned professional who needs a little structure when scouting a deal, this post will help you identify your goals, set up some guardrails, and prioritize your wish list.</p><p>Over the past couple of months, I’ve been learning about a domain I only have limited experience in: real estate investing. I’ve been keeping myself busy reading blog posts and forums and watching a stupid amount of YouTube videos while reflecting on mistakes I’ve made in my past purchases. Before I forget everything, I’ve decided to create a framework for myself so that I won’t just wing it next time.</p><h3>The Pitfalls of Emotional Investment in Real Estate</h3><p>Have you ever fallen in love with a property because ‌it was beautifully staged or had an eye-catching landscape, only to realize later that it didn’t align with your investment goals? This is a common pitfall for both new and experienced investors, and it can lead to costly mistakes. I know from personal experience that a beautiful view and a very competitive market can sidetrack anyone from noticing red flags. It got me to overlook a pretty funky and costly do-it-yourself remodel.</p><h3>The Importance of a Clear Plan</h3><p>To avoid this, it’s essential to have a clear plan before you begin touring properties, regardless of the market. By outlining your investment goals, risk tolerance, and budget, you avoid getting caught up in the moment and making decisions you regret later. Your purchasing plan will help you stay focused on the long term and ensure that your investments align with your overall financial strategy. And let’s be real: we all want less stress and higher ROI on our real estate investments, and by focusing on your clearly defined plan, you’ll be able to make faster, smarter decisions.</p><p><strong>Tip:</strong> Make sure to include a list of criteria that you will use to evaluate potential properties while on the go.</p><h3>1. Defining Your Goals</h3><p><strong>Why It’s Important</strong>: Having defined goals will keep you focused, so you don’t get sidetracked by other opportunities that might be attractive but don’t fit your current needs.</p><p>Ask yourself what your end game is and work backwards from there. Maybe you want to quit your 9–5, so cash flow is more important to you, while other investors might be focused on building equity long-term to build wealth in an appreciating asset. Possibly, you’re renting in a low-vacancy rental market and want to lower your monthly costs, where having a mortgage might be a lower monthly payment than rent.</p><p>Here is a quick breakdown of common goals for buying real estate:</p><p><strong>Long-Term Financial Goal: </strong>Do you want appreciation, cash flow, or both?</p><ul><li><strong>Cash Flow</strong>: Generate rental income in low-vacancy rental markets.</li><li><strong>Appreciation</strong>: Grow your assets with increased property value over time.</li><li><strong>Hybrid Strategy</strong>: Balancing immediate income with long-term value.</li><li><strong>Just give me a place to live: </strong>Mortgage vs renting can sometimes be cheaper, but most buyers in this bucket consider a house an investment.</li></ul><p><strong>Target Return Goal: </strong>For real estate investors, this could mean knowing how much return on investment (ROI) you expect (e.g., rental income, flip potential, or resale value).</p><p>Defining the return you aim for helps you set realistic expectations on a property. If your goal is cash flow from a multi-family property so you can retire in 10 years, you might focus on the estimated net income per unit of $300 and other metrics you care about. We won’t define all the metrics, but you’ll want to understand the possible ways you can estimate and track your target returns. The point of this post is to provide a structure for making better real estate decisions, and I’ll leave the metrics glossary to the experts.</p><h3>2. Guardrails</h3><p><strong>Why It’s Important</strong>: While most investors focus on the obvious guardrails such as purchase price or school zones, it’s important to also think about what could later impact your ROI, such as potential costs of repairs or upgrades. So maybe you will want to set up guardrails filtering out properties older than 1990 or at least figure these costs into your metrics covered in the goals section. This will help you ensure that you don’t overextend yourself financially and get carried away by that alarmingly cheap mid-century apartment complex that looks like it just needs a coat of paint to bring it to life.</p><h4>Set Up Guardrails to Avoid Emotional Decisions</h4><ul><li><strong>Budget</strong>: Define a maximum investment budget that includes purchase price, renovation costs, and reserves.</li><li><strong>Geographic Boundaries</strong>: Identify acceptable neighborhoods or locations based on your research (consider school zones, walkability, crime rates, etc.).</li><li><strong>Non-Negotiables (No-Gos)</strong>: List features that are immediate deal-breakers (e.g., flood zone locations, unpermitted work, certain property ages).</li></ul><p>Tip: If it’s not a confident yes, then it should be a confident no. Don’t talk yourself into a property that isn’t a good fit. Trust your instincts, the data, and most importantly, your plan.</p><h3><strong>3. Prioritization</strong></h3><p><strong>Why It’s Important</strong>: Unfortunately, we are not all independently wealthy (yet), so we do have to make tradeoffs with our real estate purchases. While this is just one of many prioritization frameworks, it’s easy to remember. It’s called the ​​MoSCoW method and is often used in product management to help prioritize features or functionality within a feature.</p><ul><li><strong>Must-Haves</strong>: Essential features that are non-negotiable for the investment (e.g., a minimum number of bedrooms, finished basement for Airbnb use).</li><li><strong>Should-Haves</strong>: Important features that strongly influence choice but aren’t deal-breakers (e.g., proximity to public transport, a second bathroom).</li><li><strong>Could-Haves</strong>: These are features that are desirable but don’t significantly impact the property’s value or usability (e.g., a finished basement or an updated kitchen).</li><li><strong>Won’t Haves</strong>: Clearly defined red flags that immediately eliminate a property (e.g., extensive repairs needed, located on a high-traffic street).</li></ul><p><strong>Tip</strong>: Use your list to filter when looking at properties online, and keep them on your phone to revisit them before any property tour. After looking at ten properties in one weekend, you&#39;d be surprised what you forget.</p><h3>“Slow is Smooth, and Smooth is Fast”</h3><p>As the Navy SEAL mantra goes, “slow is smooth, and smooth is fast”. In real estate, clearly defining your goals and setting limits before viewing properties will result in quicker and more confident decision-making. You can secure lower-risk deals and achieve your investment objectives faster by getting your priorities straight.</p><h4>The Advantages of Establishing and Adhering to a Plan:</h4><ul><li><strong>Faster Decisions</strong>: Eliminate hesitation with clear, early planning.</li><li><strong>Staying Within Budget</strong>: Avoid financial overextension in competitive markets.</li><li><strong>Reduced Emotional Attachment</strong>: Stay objective and avoid impulsive purchases.</li><li><strong>Long-Term Success</strong>: Align purchases with broader investment strategies.</li></ul><h3>Take Action</h3><p>Remember, I’m still learning this stuff, too, so take my recommendations with a grain of salt. But before you start looking for your first or next property, you should define your goals, guardrails, and prioritization criteria. Whether buying a dream home or investing for cash flow or appreciation, this preparation will set you up for smarter decisions and less stress down the road.</p><p><em>Post created by a tired human and edited with Writer</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a5473add8fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Short-term Rental Analysis Using CrewAI]]></title>
            <link>https://medium.com/@StevieLKim/crewai-and-me-part-2-ab63cdc755b1?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab63cdc755b1</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[agents]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Thu, 19 Dec 2024 18:26:45 GMT</pubDate>
            <atom:updated>2025-05-02T02:31:19.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*wx_k0qeEWu2L79LD.png" /><figcaption>Short-term rental metrics</figcaption></figure><p>Here I am again, folks, talking about CrewAI. But this week, I’ll share some details about the hurdles I encountered. Yes, that’s right, the hurdles I ran into, I never was much of an athlete. In <a href="https://medium.com/@StevieLKim/crewai-and-me-part-1-2fa579bcb07c">my last post</a>, I covered the basic settings and some best practices for getting started with CrewAI. In this post, I’ll share my simple research and report configurations for trends and predictions in the short-term rental market. In true “me” fashion, I’ll also expose some of the challenges I encountered and the lessons I learned along the way. Let’s dive in.</p><h3>Short-term Rentals: Market Trends and Forecast</h3><p>When I started tinkering around with CrewAI, I didn’t have a specific project in mind. I just wanted to put some of my high-level conceptual knowledge about agentic workflows to practical use. But, after I went through their <a href="https://docs.crewai.com/quickstart">Quickstart</a> guide that shows you how to build a report based on their default topic: “AI Agents,” I was inspired to wire up some of my own minions to research and report on the short-term rental forecast for 2025, complete with matplotlib charts.</p><h3>Reflection (mine, not the agents):</h3><p>While everything about using CrewAI is easy, it’s challenging to get the right mix of explicit directives while allowing the agents to make their own decisions. The point, at least to me, is not to automate what I normally do but to nudge the agents to perform tasks in a way that uncovers more information and insights than I could on my own.</p><p>To start out, I created a 1:1 relationship between 3 agents and 3 tasks, mostly because I didn’t know what I was doing. Turns out this isn’t the most effective or efficient way to design an agentic workflow because it’s slower and more prone to errors due to increased complexity.</p><p><strong>Outline of my original workflow:</strong></p><p><strong>Research Agent:</strong> Gathers data on short-term real estate trends and identifies opportunities in emerging markets.</p><ul><li><strong>Task Output:</strong> list with 10 bullet points of relevant information</li><li><strong>Configuration:<br></strong>- delegation=True<br>- tools=[file_writer_tool, file_read_tool,serper_tool]</li></ul><p><strong>Chart Agent:</strong> Generates visualizations based on raw data and reports.</p><ul><li><strong>Task Output:</strong> Matplotlib charts</li><li><strong>Configuration:<br>-</strong> tools=[file_writer_tool, file_read_tool]<br>- allow_code_execution=True</li></ul><p><strong>Reporting Agent</strong>: Synthesizes data into a markdown report containing actionable insights for investors.</p><ul><li><strong>Task Output: </strong>Comprehensive report in markdown</li><li><strong>Configuration:<br></strong>- delegation=True<br>- tools=[file_writer_tool, file_read_tool]</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*i7t4WzTcWbX1epHRT1_tbQ.png" /></figure><p>As I didn’t think to use version control until later, I don’t have the exact settings for my initial setup. However, I admit there was a chaotic mess of verbose task descriptions with multiple iterations before I got my desired result. While the markdown reports were created, the content was too brief to be called a “robust report.” But I had bigger issues.</p><h4>Charts: Sometimes You See Them, Sometimes You Don’t</h4><p>One of the first ongoing issues I encountered was that sometimes the charts would be created, while at other times they weren’t. And when they were, they were in multiple directories.</p><p>For the problem of the occasional missing charts, I extended the retries from the default “2” to “5” for my Research Agent, who wrote the files necessary for the Reporting Agent, since I thought maybe the Reporting Agent was trying to create the reports too soon. This provided consistency.</p><pre>max_retry_limit=5</pre><p>Some of the charts created weren’t exactly helpful. ‌Sometimes the charts would be labeled <em>City A</em>, City B, etc. while others had the actual city names.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*T3bd35QbS2UNcakO" /><figcaption>The offending charts with simulated data</figcaption></figure><p>I probably should have explicitly told my agents that when performing a task, if they can’t find relevant data, don’t make it up.</p><p>So, I added to my Research Task’s description:</p><p><em>If you cannot find any data from your online searches, don’t create fake data, but instead, retry your search.</em></p><p>This fixed the issue, and I got useful charts, but they were still in the wrong directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Nm6YAnmXv19ysKMX" /></figure><p>To get the charts and the files in the same directory, I explicitly defined the required file name and directory using the Task attribute <em>output_file,</em> which caused unexpected behavior. Sometimes, the agents saved the chart files to the parent directory, sometimes to the directory None, and sometimes to a directory called <em>Data</em>.</p><p>Troubleshooting I looked into the different agent and task settings. I already had delegation=True, which should have ensured that tasks have the necessary context to generate and incorporate charts into the report.</p><p>I then explored using the context attribute for tasks to specify which outputs should serve as inputs for subsequent tasks. That didn’t work and only caused more inconsistencies. So, I stopped adding stuff and thought about how I had designed the agent-to-task relationship.</p><p>On top of the strange chart behavior, the workflow was slower than I expected it to be, so I removed the Chart Agent and assigned the Chart Task to the Reporting Agent.</p><p>This provided a 1:1 and 1:2 relationship between agents and tasks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ZILhv0v4msVQ7vU" /></figure><p>This had a couple of beneficial side effects. The charts were created faster (expected), but unexpectedly, the charts now appeared in the same directory that the markdown files were written to!</p><p>Basically, it seems that even though I had delegation=True, and the context attribute set to the appropriate tasks, there was still missing context between the original 3 agents. Having the Reporting Agent deliver both the charts and the report while relying only on the Research Task’s output solved the problem.</p><p><em>I asked ChatGPT about my observations:</em></p><p>“Studies indicate that while multi-agent systems can enhance task success rates and productivity, they also introduce complexities and overhead in coordinating multiple specialized agents at scale. This suggests that overly granular decomposition may lead to diminishing returns, as the coordination overhead can offset the benefits of specialization.</p><p>Additionally, research on multi-agent reinforcement learning highlights that as the number of agents increases, managing interactions and ensuring well-coordinated activities becomes more complex, potentially impacting system performance (source:<a href="https://aws.amazon.com/blogs/aws/introducing-multi-agent-collaboration-capability-for-amazon-bedrock/"> AWS Multi-Agent Collaboration</a> and<a href="https://arxiv.org/abs/2302.05007"> ARXIV Multi-Agent Learning</a>).”</p><p>Of course, I’ve watched talks and read blog posts saying the same thing, but when you are down the rabbit hole late at night, sometimes it’s easy to forget the basics.</p><p>Since the charts were properly labeled, my agents were running around performing their tasks quicker, and my charts and markdown file were written to the same directory, I returned to getting the agents to write them to a directory that I specified. Recall that I mentioned that explicitly stating the output file path didn’t work, so, in a fit of desperation, I stated it as natural language:</p><blockquote>expected_output: &gt;<br> Matplotlib charts should be saved in “reports” directory.</blockquote><p>Unexpectedly, it worked, even though setting the explicit directory path with o<em>utput_file</em> threw errors. CrewAI is full of surprises.</p><p>Last night, I tested a 1:2 relationship between agents and tasks by splitting up the tasks into 4 tasks. I now have a 1:2, 1:2 relationship. While this didn’t produce better results, it generated fewer errors when creating the data files and charts.</p><p>Here are the latest configurations for my agents in my crew:</p><pre> @agent<br> def research_agent(self) -&gt; Agent:<br>  return Agent(<br>   config=self.agents_config[&#39;research_agent&#39;],<br>   llm=llm,<br>   tools=[file_writer_tool, file_read_tool,directory_read_tool,serper_tool,web_search_tool],<br>   allow_code_execution=True,<br>   allow_delegation=True,<br>   max_execution_time=300,<br>   max_retry_limit=5<br>  )<br> @agent<br> def reporting_agent(self) -&gt; Agent:<br>  return Agent(<br>   config=self.agents_config[&#39;reporting_agent&#39;],<br>   llm=llm,<br>   tools=[file_writer_tool, file_read_tool,directory_read_tool],<br>   allow_code_execution=True,<br>   allow_delegation=True,<br>   max_execution_time=300,<br>   max_retry_limit=5<br>  )</pre><p>If you are curious about my Agent and Task prompts and other configurations, you can find them in the <a href="https://github.com/stevielkim/REIAnalyst">GitHub repo</a> for this project. If you want the results, you can view two versions of the generated reports at the end of this post.</p><h4>Summary</h4><p>While it’s been fun experimenting, the results didn’t provide alternative insights to what I already knew about short-term rental trends. Also, the revenue and average daily rate aren’t accurate, but they aren’t so far off that I mind too much. None of this is too surprising, but with a few prompts in ChatGPT I got the same thing minus the data visualizations. So why use agents vs gpts? The autonomous parts, of course. Agents can interact with their environment in a way that gpts cannot. They can collaborate, delegate, and make decisions without explicit instructions as long as you put the right guardrails up to help them stay on task.</p><p><strong>Tips for Success</strong></p><ul><li>Test using fewer agents for potentially faster execution</li><li>Balance explicit directives with flexibility</li><li>For complex coding agents use max_retry_limit and max_execution_time for higher than the defaults</li><li>Leverage Git to track changes</li><li>Use the “planning” attribute, which helps control the task sequence</li><li>Try using the hierarchical process as a manager (I haven’t yet, but plan to)</li></ul><p><strong>Things to watch out for</strong></p><ul><li>Coding Agents make a ton of syntax errors, so set max_retries higher than the default “2”</li><li>You won’t always know if something goes wrong, so write the output to logs to help you debug</li><li>Don’t fully rely on the CrewAI doc AI search functionality since it told me that memory is enabled by default, which is not accurate.</li></ul><p><strong>Things I want to see</strong></p><ul><li>CrewAI auditing capabilities with built-in logging</li></ul><h4>Next Steps</h4><p>Of course I saw a <a href="http://deeplearning.ai/">CrewAI DeepLearning.AI</a> course the day I finished writing this post, but that’s what I get for going straight to developer docs. I’m sure it shares what to do and not to do and would have saved me a lot of time with better results, so that’s what I’ll check out next. While I’m not convinced my particular use case is worthy of the environmental cost of iterating and running LLMs, it does provide an example of what agentic workflows can accomplish, especially for non-developers using low-code tools such as CrewAI.</p><p>What are your thoughts on use cases for agentic workflows? Any real-world use cases for problems that agents are uniquely poised to solve?</p><p><em>If you’re hiring for product-related roles, I’d love to connect and discuss how I could contribute to your team!</em></p><p>Here are two versions of the report with slight variations to the prompts (note the first version is not on GitHub, while the second version is).</p><h3>Short-term Rental Real Estate Investment Projections — 2025</h3><h3>Introduction</h3><p>The short-term rental market continues to evolve as a dynamic sector within the real estate industry. As we approach 2025, investors seek to understand the potential trajectories of key markets. This report provides a comprehensive analysis of the market trends observed in 2024 and projects future opportunities. We have examined average daily rates, occupancy rates, revenue per available room, and visitor growth percentage across major U.S. cities.</p><h3>2024 Market Recap</h3><p>Throughout 2024, the short-term rental sector displayed resilience and growth. Our analysis focused on five cities: New York, Los Angeles, Miami, Chicago, and San Francisco. New York led with the highest average daily rate of $220 and a revenue per available room of $180. Miami attracted the highest visitor growth at 5.5%, highlighting a burgeoning interest likely to influence future demand.</p><h3>Key Insights</h3><ul><li><strong>New York</strong>: Dominated high-pricing brackets with strong occupancy at 82%, consolidating its position as a premium market.</li><li><strong>Los Angeles</strong>: Despite moderate growth (3.8%), it maintained steady demand, bolstered by its expansive tourist infrastructure.</li><li><strong>Miami</strong>: Emerged as a significant developing market with robust visitor growth, indicating expanding demand and promising investment potential.</li><li><strong>San Francisco and Chicago</strong>: Continued to hold stable mid-range positions; however, San Francisco’s higher average rates align with its tech-driven economy.</li></ul><h3>2025 Projections</h3><p>Looking forward to 2025, several factors are poised to influence the short-term rental market trajectory:</p><p><strong>Economic Conditions</strong>: The ongoing economic recovery is expected to support increased traveler activity, benefiting occupancy rates, especially in leisure-driven locations such as Miami.</p><p><strong>Technological Advances</strong>: Innovations in property management systems and digital marketing will streamline operations, potentially boosting revenue generation capabilities.</p><p><strong>Regulatory Environment</strong>: Attention to local regulations remains crucial. Cities tightening short-term rental policies could face stagnated growth, while diplomatically managed locales might see expansion.</p><p><strong>Sustainability Concerns</strong>: Eco-friendly properties are likely to attract environmentally conscious travelers, introducing a niche market segment.</p><h3>Actionable Insights</h3><ol><li>Investors should prioritize Miami for growth-oriented investments, taking advantage of its rising demand and visitor growth.</li><li>High-value opportunities persist in New York, although competitive pricing necessitates differentiation strategies.</li><li>Innovations in service delivery and guest experience, leveraging technology, can enhance competitiveness across markets.</li><li>Monitor local regulations to foresee potential impacts on short-term rental availability and profitability.</li><li>Expansion into eco-friendly, sustainable properties aligns with emergent market trends, offering additional investment avenues.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUvqO1e0CDl8IvKA9g6inA.png" /></figure><p>This chart illustrates city-specific performance metrics, underscoring areas of robust growth and stable demand, serving as a visual guide to investment decision-making.</p><h3>Conclusion</h3><p>As the short-term rental market braces for 2025, strategic investments guided by data-driven insights will be pivotal. With proper positioning and an adaptive approach to evolving market conditions, investors stand to leverage substantial opportunities in this dynamic economic landscape.</p><h3>Sources</h3><ul><li>Market data derived from analysis and projections based on the structured 2024 dataset.</li><li>Research insights compiled from industry reports and proprietary data.</li></ul><p>By maintaining an analytical focus, strategic foresight, and adaptability, stakeholders can navigate the complexities of the 2025 short-term rental market confidently.</p><h3>2025 U.S. Short-Term Rental Market Investor Report</h3><h3>Market Trends and Insights</h3><p>The U.S. short-term rental market is poised for significant growth in 2025, with demand expected to increase by 4.9%, surpassing the supply growth of 4.7%. This trend is particularly evident in urban markets such as New York, Washington, D.C., San Francisco, and Atlanta. These cities are anticipated to experience gains in occupancy and revenue per available room (RevPAR), driven by limited supply growth and regulatory constraints. As urban areas continue to attract travelers, investors can expect stable returns in these high-demand locations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*U1AFxPTnr1moOu0pltfV2g.png" /></figure><h3>Promising Cities for Investment</h3><p>Investors looking to capitalize on the short-term rental market should consider focusing on cities with high occupancy rates and limited new supply. New York, for instance, boasts high occupancy rates, with regulatory constraints further limiting new supply. Washington, D.C. offers steady demand growth with minimal new supply, making it an attractive option for investors. San Francisco presents strong RevPAR growth potential, while Atlanta benefits from increasing demand and stable economic conditions. These cities offer promising opportunities for investors seeking to maximize returns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*L__EVXimXbyDSqz1fGmmhg.png" /></figure><h3>Key Metrics by City</h3><p>Key metrics such as average daily price, occupancy rate, and revenue per available room vary by city, with urban areas generally commanding higher rates. New York leads with an average daily price of $250, followed by San Francisco at $270. Occupancy rates are expected to stabilize and grow in major urban markets, with San Francisco leading at 78%. Revenue per available room is projected to increase in key cities as demand continues to outpace supply, offering lucrative opportunities for investors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*MqvJXz3s5c1mOhxnJc3SKQ.png" /></figure><h3>Economic Indicators</h3><p>The economic conditions in 2025 are expected to support the growth of the short-term rental market. Rising real incomes and steady economic conditions will likely bolster demand growth. Although interest rates are projected to remain high, stronger cash flow and home value appreciation provide substantial investment opportunities. Investors should consider these economic indicators when evaluating potential investments in the short-term rental market.</p><h3>Sources</h3><ol><li><a href="https://www.airdna.co/outlook-report">AirDNA 2025 Outlook Report</a></li><li><a href="https://www.hotelnewsresource.com/article134372.html">Hotel News Resource</a></li><li><a href="https://money.usnews.com/investing/articles/best-places-to-invest-in-real-estate">US News Money — Best Places to Invest in Real Estate</a></li></ol><p>This report provides a comprehensive overview of the U.S. short-term rental market for 2025, highlighting key trends, promising investment areas, and essential metrics for investors. By leveraging these insights, investors can make informed decisions to capitalize on the opportunities within the market.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab63cdc755b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agentic Workflows Using CrewAI]]></title>
            <link>https://medium.com/@StevieLKim/crewai-and-me-part-1-2fa579bcb07c?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fa579bcb07c</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Fri, 13 Dec 2024 15:41:04 GMT</pubDate>
            <atom:updated>2025-05-02T02:36:36.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpLnY_EZO4AMn0pVdY0QKw.png" /><figcaption>I spent a decent wad of my imaginary eco-dollars convincing ChatGPT not to make a sexy work look for me. It turned out awesome and now I want that fit.</figcaption></figure><p>In a nutshell, autonomous agents are self-contained units designed to perform actions, make decisions, and execute tasks based on specific roles, goals, and expertise defined by you or me. In the first of a two-part series, I will cover the core concepts of an agentic framework called <a href="https://www.crewai.com/">CrewAI</a>. In my next post, I’ll share my experiences creating a research and reporting project with auto-generated charts using the framework. Per usual, I’ll expose all my stumbles and fumbles along the way, so stay tuned.</p><p>After completing a product discovery initiative on agentic workflows, I finally got the time to play around with a framework that makes creating multi-agent orchestration crazy easy. <a href="https://www.crewai.com/">CrewAI</a> is part of the growing list of agentic frameworks designed to facilitate the creation of complex workflows by enabling agents to collaborate effectively through communication and delegation. By breaking down processes into manageable components, CrewAI facilitates efficient task execution across domains like data analysis, content generation, and beyond. Even those with minimal Python experience could handle it with some ambition.</p><p>Since there is a ton of material already out there on agentic workflows, I won’t cover anything complex here, but if you aren’t familiar with the idea of assigning little minions specific tasks to accomplish and have them reflect, collaborate, and delegate, then take a beat to read or watch some of the true experts teaching this stuff like <a href="https://www.linkedin.com/in/andrewyng/">Andrew Ng</a> or the folks over at <a href="https://www.youtube.com/@LangChain">LangChain</a>.</p><h3>CrewAI Overview</h3><p>As I began experimenting with CrewAI, my goal was to better understand how autonomous agents can be leveraged to streamline workflows, especially the annoyingly time-consuming ones. Because it was so easy to use, CrewAI allowed me to think critically about how I designed and iterated on my agents and their tasks. I’m joking. I pressed buttons for a few hours until something worked, but at least I documented it!</p><h4>Installing CrewAI</h4><p>Just follow the <a href="https://docs.crewai.com/installation">Installation</a> guide from CrewAI, and you should have no problems getting up and running quickly. But, if you’re like ‌me, there’s no such thing as getting up and running without at least one version conflict.</p><p>As I was trying to install crewai_tools in my virtual environment, I got the following error:</p><blockquote>ImportError: cannot import name ‘SerperDevTool’ from ‘crewai_tools’</blockquote><p>But setting specific versions for “crewai” and “crewai_tools”<a href="https://github.com/crewAIInc/crewAI/issues/762"> fixed the issue</a> quickly.</p><blockquote>pip install crewai==0.28.8 crewai_tools==0.1.6 langchain_community==0.0.29</blockquote><h4>Key Concepts: Crews, Agents and Tasks</h4><ul><li><strong>Crews</strong> oversee workflows, manage agent collaboration, and deliver outcomes, with the option to enable memory for continuity across tasks.</li><li><strong>Agents</strong> are autonomous units with defined roles, goals, and expertise, capable of executing multiple tasks and retaining memory when enabled.</li><li><strong>Tasks</strong> are the specific assignments agents complete, with detailed execution parameters and opportunities for collaborative execution.</li></ul><p>Together, these components create a modular and flexible framework for handling complex workflows. While CrewAI has other, more advanced capabilities, I haven’t explored them yet, so perhaps I’ll discuss hierachical processes, memory management, and custom tools in a future post.</p><h3>Agent Settings</h3><p>To begin, you’ll want to refactor the agents.yaml file to suit your project’s needs. I recommend starting with simple changes to the template provided by CrewAI, because the more you tweak the wording, the more likely your agent will go off the rails. Just follow the <a href="https://peps.python.org/pep-0020/">Zen of Python</a> and you should be fine. Depending on your project, you may need to update all of the agents’ directives. However, to begin experimenting, I suggest playing around with the default settings first.</p><h4>Core settings for agents</h4><ul><li><strong>Role: </strong>Clearly define the specific role or function of the agent, such as researcher, writer, or coder.</li><li><strong>Goal</strong>: Provide clear, concise instructions to guide decision-making.</li><li><strong>Backstory</strong>: Offer context to aid interactions with other agents and enhance collaboration.</li></ul><p>There are a ton of other <a href="https://docs.crewai.com/concepts/agents#agent-attributes">settings</a> available to agents which can be useful, such as enabling delegation. Just set “allow_delegation: true” to enable agents to work together and delegate tasks seamlessly. According to CrewAI’s AI search, by enabling delegation you get:</p><ul><li>Enhanced Functionality: Delegation amplifies the crew’s overall capability by allowing agents to intelligently distribute tasks based on expertise.</li><li>Efficient Problem-Solving: It promotes collaborative problem-solving, enabling agents to leverage each other’s strengths.</li></ul><p>Honestly, I want to test this out more because I didn’t see a significant difference in quality, but I didn’t conduct a proper test, so I can’t confidently make that assessment.</p><h4>Task Settings</h4><p>Now you can setup your <a href="https://docs.crewai.com/concepts/tasks">Tasks.yaml</a> file where you can define the actions Agents will take and set various properties, like forcing your minion Agents to play nice together to get Tasks done. Just like with Agents, there are a ton of fun <a href="https://docs.crewai.com/concepts/tasks#task-attributes">attributes</a> to dig into, but the basic ones you’ll want to know are:</p><ul><li><strong>Description: </strong>What the task accomplishes and any guardrails such as researching only the past 5 years of a topic</li><li><strong>Expected_Output:</strong> The output of the task, or definition of done such as a markdown file or chart</li><li><strong>Agent:</strong> The agent responsible for running the task</li><li><strong>Output_file: </strong>The file and path you want the task to write output to</li><li><strong>Context: </strong>Other Task’s outputs that you want the current Task to rely on</li></ul><h4>Crew Settings</h4><p>Here’s where you assign your Agents and your Tasks to the <a href="https://docs.crewai.com/concepts/crews#crew-attributes">Crew</a> along with any other configurations such as Process, Cache, Tools, etc. Note that here is where you would also add handy Agent attributes such as:</p><ul><li>allow_code_execution=True</li><li>allow_delegation=True</li></ul><h4>Main.py Settings</h4><p>This is where you update the default “Topic” with your own.</p><h3>General CrewAI Tips</h3><ul><li><a href="https://docs.crewai.com/concepts/tools">CrewAI Tools </a>such as file reading and writing can be attributed to either Agents or Tasks, but since one Agent can execute multiple tasks, it’s more flexible to assign the tool to an Agent. However, if only one Task needs the Tool and one Agent is assigned multiple Tasks, then it’s more performant to only add the Tool to the Task that requires it.</li><li>Flexibility: I suggest specificity when setting your CrewAI “topic” value in the main.py file. This way, you can swap out “topic” without changing anything else. For example, you can easily update “topic” from “short-term real estate rentals” to “High dividend ETFs” while your Agent and Task verbiage refers to “research and report on {topic} investments.”</li><li>Versioning: I highly recommend using Git for version control, not only for the codebase but also for artifacts generated during each iteration. CrewAI doesn’t offer the ability to reproduce your results, so if you want to properly test out your changes and have the ability to revert any issues, I suggest doing what I say, not what I do (or don’t do in this case).</li></ul><p>I barely scratched the surface of what CrewAI has to offer, but it’s late, and I have to finish writing Part 2 of this series. In it, I’ll share my experiences on my research and report workflow, and I’ll push my code and files to GitHub for anyone to take a look at.</p><p><strong>Shameless Plug:</strong> If you’re hiring for product-related or customer-facing roles, <a href="https://www.linkedin.com/in/stephanielkim/">I’d love to connect</a> and discuss how I could contribute to your team!</p><p><em>Written by a tired human and edited by Grammarly &amp; Writer, so blame those two for errors.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fa579bcb07c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring Essentialism: If it’s not a “Hell Yes!” Then it’s a “Hell No!”]]></title>
            <link>https://medium.com/@StevieLKim/exploring-essentialism-if-its-not-a-hell-yes-then-it-s-a-hell-no-7629831fcdf0?source=rss-9b24350854e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7629831fcdf0</guid>
            <category><![CDATA[business-books]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[books-and-authors]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Stevie Kim]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 14:40:07 GMT</pubDate>
            <atom:updated>2024-12-11T14:40:07.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xCCCcORXMWNjM3YSCKrM-A.png" /><figcaption>Dall-E 3 via ChatGPT threw me this for my blog post, and I’m not mad about it.</figcaption></figure><p>Welcome to my second post in the series, where I reflect on the book Essentialism: The Disciplined Pursuit Of Less by Greg McKeown. If you missed <a href="https://medium.com/@StevieLKim/learning-and-reflecting-on-essentialism-by-greg-mckeown-903b6472eabc">last week’s post</a>, check it out because I summarized and reflected on the book’s first chapter, Essence. Now, I’ll dive into the second chapter, Explore, where I’ll, yes, explore McKeown’s ideas around deciding what is important.</p><blockquote>“If it isn’t a clear <em>yes</em>, then it’s a clear <em>no</em>.”</blockquote><h3><strong>Explore: Discern What Is Important</strong></h3><p>Within the section “Explore” are the chapters Escape, Look, Sleep, Play, and Select, and if you are confused, so was I. Maybe I still am. I read and reread this section to discern what the focus was in relation to Essentialism, but it still feels like random fridge leftovers thrown in a soup pot and hoping for the best. But I’ll try to synthesize the main points as I understand them.</p><p>As a reminder from the last post, McKeown calls us to recognize that if everything is important, then nothing is. Anyone in enterprise SaaS understands that pain. But, by focusing on a few best practices, such as slowing down and intentionally listening to others, asking clarifying questions, and removing ourselves from the noise long enough to think clearly, we will be far more productive and efficient than if we kept pushing forward with blinders on.</p><p>To identify what truly matters, McKeown suggests we dedicate more time to playful activities, disconnect from distractions, prioritize adequate sleep, and pay attention to details others might overlook. Then, we can set our “extreme criteria” to decide where to spend our focus. This criteria comes down to what we cannot do without and gives us the courage to walk away if an opportunity does not meet that criterion. This section reminded me of the 5 Why’s (or vertical questioning) because these frameworks teach us to slow down, check our assumptions at the door, and get to the root of the problem, need, or opportunity. This, in turn, helps us focus on what’s most important to us and others.</p><p>McKeown proposes a test he calls the 90% rule. To use this rule, consider the most crucial criteria for a decision and assign scores to each option on a scale of 0% to 90%. Then, throw out anything under 90%. This only works if you have a lot of criteria to score against, which doesn’t apply to many situations, so I prefer some of his other tests, such as asking yourself, “Do I really love this?” Or, using TED speaker Derek Silvers&#39;s criteria, “It’s either HELL YEAH! Or No.” Whatever framework is used, we can be more confident in a world of uncertainty and make decisions that align with what is most important to us.</p><p><em>Reflection: </em>We’ve all been guilty of getting caught up in situations that sounded great at the time. Maybe someone stroked our ego to convince us of something, or maybe we were pressured into making a fast decision without the time and space to think it through. Whatever the external influence, we’ve all asked ourselves, “Why did I say yes?” a time or two.</p><p><em>Change habits: </em>This goes back to some of my musings in <a href="https://medium.com/@StevieLKim/learning-and-reflecting-on-essentialism-by-greg-mckeown-903b6472eabc">my last post</a> about the book. By challenging ourselves to commit to the problems we are willing to take on, acknowledging the trade-offs between choices, and deciding what we want to go all in on, we can focus on what’s important to us. That is why I like asking myself: “Is this a hell yes?” Because it helps reduce the likelihood of getting caught in analysis paralysis and can be used when we don’t have the luxury of time and space to consider our choices. This approach relies on gut instinct and doesn’t allow for any monkey business our brains might attempt to contrive.</p><p><em>Work Focus:</em> If I’m negotiating with a customer, I can’t just think well, if it’s not a “hell yes,” then it’s a “hell no.” While I like that framework for personal decisions, such as choosing a job or going on a date, we need a more robust framework for work. I think this is where the 90% rule can be useful.</p><p><em>Example: </em>Suppose your ideal customer profile (ICP) is based on firmographic criteria, such as companies with annual revenue exceeding $2 billion, a global presence, operations in highly regulated industries, and a budget allocation of at least 3% of their total revenue. We’ll use these firmographics as our “extreme criteria” for customers invited to join our customer advisory board (CAB). These individuals must also match our target persona with a director-level title. We will then send invites to only the customers who meet at least 90% of the criteria. This means that fewer people will get invited, and even fewer will say yes than we would like, but we accept that trade-off because we’d rather get great feedback and understanding than fill seats for the sake of appearances.</p><h4>Big Takeaway: Go big, or go home…or go to sleep.</h4><p>Remember what McKeown talked about in the <a href="https://medium.com/@StevieLKim/learning-and-reflecting-on-essentialism-by-greg-mckeown-903b6472eabc">first chapter</a> about choices? Sometimes, we must choose to play over sending that email, sleep rather than work late, listen over talking, and go dark versus answering Slack. Taking care of our little brains, our big hearts, and our tired souls will help us understand what is essential to us and those we interact with. And then, when a pretty good opportunity comes around, we can confidently say, “Hell No!” Because it’s not a “Hell Yes!”</p><p><em>Written by a tired human and edited by Grammarly, so blame it for errors and propriety.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7629831fcdf0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>