• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

What’s up everyone, today we have the pleasure of sitting down with Kim Hacker, Head of Business Ops at Arrows.

Summary: Tool audits miss the mess. If you’re trying to consolidate without talking to your team, you’re probably breaking workflows that were barely holding together. The best ops folks already know this: they’re in the room early, protecting momentum, not patching broken rollouts. Real adoption spreads through peer trust, not playbooks. And the people thriving right now are the generalists automating small tasks, spotting hidden friction, and connecting dots across sales, CX, and product. If that’s you (or you want it to be) keep reading or hit play.

In this Episode…

• Most AI Note Takers Just Parrot Back Junk
• Why Most Teams Will Miss the AI Agent Wave Entirely
• When AI Systems Meet The Chaos Of Actual Workplace Processes
• How Effective AI Tools Minimize Distance Between Information And Action
• Why Tool Consolidation Fails Without Team Member Interviews
• Reframe Tool FOMO by Setting Clear Priorities and Capturing Curiosity
• How to Build AI Skills If You Feel Like You’re Falling Behind
• Why Generalists Are Thriving in the Age of AI

About Kim

• Kim started her career in various roles like Design intern and Exhibit designer/consultant
• She later became an Account exec at a Marketing Agency
• She then moved over to Sawyer in a Partnerships role and later Customer Onboarding
• Today Kim is Head of Business Operations at Arrows

Most AI Note Takers Just Parrot Back Junk

Kim didn’t set out to torch 19 AI vendors. She just wanted clarity.

Her team at Arrows was shipping new AI features for their digital sales room, which plugs into HubSpot. Before she went all in on messaging, she decided to sanity check the market. What were other sales teams in the HubSpot ecosystem actually *doing* with AI? Over a dozen calls later, the pattern was obvious: everyone was relying on AI note takers to summarize sales calls and push those summaries into the CRM.

But no one was talking about the quality. Kim realized if every downstream sales insight starts with the meeting notes, then those notes better be reliable. So she ran her own side-by-side teardown of 22 AI note takers. No configuration. No prompt tuning. Just raw, out-of-the-box usage to simulate what real teams would experience.

“If the notes are garbage, everything you build on top of them is garbage too.”

She was looking for three things: accuracy, actionability, and structure. The kind of summaries that help reps do follow-ups, populate deal intelligence, or even just remember the damn call. Out of 22 tools, only *three* passed that bar. The rest ranged from shallow summaries to complete misinterpretations. Some even skipped entire sections of conversations or hallucinated action items that never came up.

It’s easy to assume an AI-generated summary is “good enough,” especially if it sounds coherent. But sounding clean is not the same as being useful. Most note takers aren’t designed for actual sales workflows. They’re just scraping audio for keywords and spitting out templated blurbs. That’s fine for keeping up appearances, but not for decision-making or pipeline accuracy.

Key takeaway: Before layering AI on top of your sales stack, audit your core meeting notes. Run a side-by-side test on your current tool, and look for three things: accurate recall, structured formatting, and clear next steps. If your AI notes aren’t helping reps follow up faster or making your CRM smarter, they’re just noise in a different font.

Back to the top ⬆️

Why Most Teams Will Miss the AI Agent Wave Entirely

The vision is seductive. Sales reps won’t write emails. Marketers won’t build workflows. Customer success won’t chase follow-ups. Everyone will just supervise agents that do the work for them. That future sounds polished, automated, and eerily quiet. But most teams are nowhere close. They’re stuck in duplicate records, tool bloat, and a queue of Jira tickets no one’s touching. AI agents might be on the roadmap, but the actual work is still being done by humans fighting chaos with spreadsheets.

Kim sees the disconnect every day. AI fatigue isn’t coming from overuse. It’s coming from bad framing. “A lot of people talking about AI are just showing the most complex or viral workflows,” she explains. “That stuff makes regular folks feel behind.” People see demos built for likes, not for legacy systems, and it creates a false sense that they’re supposed to be automating their entire job by next quarter.

“You can’t rely on your ops team to AI-ify the company on their own. Everyone needs a baseline.”

Most reps haven’t written a good prompt, let alone tried chaining tools together. You can’t go from zero to agent management without a middle step. That middle step is building a culture of experimentation. Start with small, daily use cases. Help people understand how to prompt, what clean AI output looks like, and how to tell when the tool is lying. Get the entire org to that baseline, then layer on tools like Zapier Agents or Relay App to handle the next tier of automation.

Skipping the basics guarantees failure later. Flashy agents look great in demos, but they don’t compensate for unclear processes or teams that don’t trust automation. If the goal is to future-proof your workflows, the work starts with people, not tools.

Key takeaway: If your team isn’t fluent in basic AI usage, agent-powered workflows are a pipe dream. Build a shared baseline across departments by teaching prompt writing, validating outputs, and experimenting with small use cases. That way you can unlock meaningful automation later instead of chasing trends that no one has the capacity to implement.

Back to the top ⬆️

When AI Systems Meet The Chaos Of Actual Workplace Processes

AI vendors keep shipping tools like everyone has an intern, a technical co-pilot, and five extra hours a week to configure dream workflows. The real buyers? They’re just trying to fix broken Salesforce fields, write one less follow-up email, or get through the day without copy-pasting notes into Notion. Somewhere between those extremes, the user gets lost in translation.

Kim has felt that gap from both sides. She was hesitant to even start with ChatGPT. “I almost gave up on it,” she said. “I felt late and overwhelmed, and I just figured maybe I wasn’t going to be an AI person.” Fast forward to today, and it’s one of her most-used tools. She didn’t get there by wiring up agents. She started small. Simple things. Drafting ideas, summarizing content, clarifying messy thoughts. That built trust. Then momentum.

“There’s a lot that has to happen before your calendar is filled with calls and nothing else. AI can help, but you have to let it earn its spot.”

If you’re trying to build that muscle, forget the multi-tool agent orchestration for a second. Focus on everyday wins like:

• Turning a messy Slack thread into a clean summary
• Writing a follow-up email in your tone
• Rewriting a calendar event title so it makes sense to your future self
• Cleaning up action items from a sales call without hallucinations
• Drafting internal documentation from bullet points

The pace is accelerating. People feel it. You don’t need to watch keynote demos to know that change is coming fast. It’s easy to feel like you’re already behind. Kim doesn’t disagree. She just thinks most teams are solving the wrong problem. Vendors are focused on the sprint. Most people haven’t even laced up. “Everyone wants the big leap,” she said. “But most wins come from small, boring tools that actually do what they say they’ll do.”

That’s the root issue. A lot of AI features today are solving theoretical problems. They assume workflows are tidy, perfectly tagged, and documented in Notion. Real work is messier. It happens in Slack threads, half-filled records, and follow-ups that never got logged. If your tool can’t handle that, then it doesn’t matter how shiny your roadmap is.

Key takeaway: Stop evaluating AI features based on potential. Evaluate them based on current chaos. Ask whether the tool handles your worst-case scenario, not your ideal one. Prioritize small, boring use cases that save time immediately. That way you can build trust, reduce friction, and create space to actually experiment with bigger bets later.

Back to the top ⬆️

How Effective AI Tools Minimize Distance Between Information And Action

Demos lie. Or at the very least, they leave out the messy parts. Kim ran 22 AI note takers through the same sales call to find out which ones actually deliver something useful when it’s not a curated product walkthrough. No prep, no prompting, no cherry-picked moments. Just a standard sales call with real-world distractions—casual small talk, a few acronyms, and a joke about toilet-training a cat.

What she found wasn’t surprising, but it was deeply frustrating. Most tools failed the sniff test. They stuffed three pieces of useful context into a bloated paragraph of nothingness. Others hallucinated action items. A bunch included completely irrelevant small talk. Many summarized everything except the actual decision-making content. When your note taker highlights a trip to Italy but forgets the agreed-upon launch timeline, something’s broken.

“It’s like they’re wrapping three decent facts in a blanket of junk just to look more intelligent.”

Only three tools passed with flying colors: Fathom, Grainola, and Circleback. Each one delivered crisp, skimmable, high-utility notes right out of the box. They consistently identified:

• Key stakeholders and decision makers
• Pain points actually discussed
• Specific next steps and action items
• Clear dates or timelines
• Irrelevant chatter removed entirely

These weren’t vague summaries either. They read like usable follow-up material. No digging through recordings. No CTRL+F on transcripts. Just real notes that match how real people follow up on calls.

Kim also pointed out how most vendors over-hype their “Ask AI” features. It sounds powerful. A smart chat layer that can answer questions about your meeting. But these features are reactive by design. They assume the user has the time and clarity to stop, phrase a question, and do something with the answer. The better path is proactive tooling that observes the context and offers help before you even know what you need. That’s how her team at Arrows is approaching it. If a prospect mentions scheduling a trial kickoff, the system detects that and offers to add it to a milestone. You didn’t have to ask. It just helped.

The real benchmark for AI productivity tools isn’t how clever they sound. It’s how little friction they introduce between the moment something important happens and the moment it’s acted on. Every additional step like prompting, rephrasing, validating, costs time and attention. That’s where most vendors fail. They build for people who have unlimited capacity to play with features instead of professionals trying to finish their day without dropping balls.

Key takeaway: Great AI doesn’t wait to be asked. It listens, it filters, and it acts when your focus is somewhere else. If a tool forces you to dig through fluff, manually trim notes, or craft perfect prompts just to get value, it’s slowing you down. Prioritize tools that proactively help you move work forward without making you think too hard. And always run your own messy test calls, because demos are built for hype, not for chaos.

Back to the top ⬆️

How Agent Workflows Turn Conversation Intelligence Into Automated Action

AI note takers love to flex transcripts and shiny meeting summaries, but very few are built with real work in mind. CS and sales ops folks are slammed with back-to-backs. They don’t have time to sift through a wall of bullet points or scan a summary that reads like a middle-school book report. What they need is precision, not a wall of text. What they get is another inbox.

Some tools are finally catching up. The better ones integrate with HubSpot and extract specific, useful context (like budget, decision criteria, or key blockers) and push it directly into CRM properties. That way the next person in the workflow actually sees what matters. Kim described a basic but essential move: sales logs pain points, AI stores those in a structured field, and CS picks up the thread without making the customer repeat themselves.

“If the sales team uncovered pain points in the sales process, fill a property and have that sit in the CRM so the CSM can see what the pain points are.”

You don’t need more AI summaries. You need outputs that do something. Some tools now convert spoken commitments into actual tasks. Say “I’ll send over that deck” and the system logs it, assigns it, and tracks it inside HubSpot or Asana. You get real follow-through without needing a second brain or post-call cleanup. And when that context is in the CRM, you unlock automation: reminders, escalations, follow-up campaigns—all without chasing people around Slack.

There’s also an emerging layer of agent-style workflows. If the AI detects it was a sales call, it can route outputs to the right team. If it spots blockers or objections, it can flag them or kick off an escalation path. The logic is simple: if X is said, then Y gets done. These tools are learning how to act on intent. But if the source notes are garbage, none of it matters. Garbage in still means garbage out, and teams can’t automate their way around bad data.

Key takeaway: AI note takers that matter are the ones that push usable context into the systems people already live in. Build workflows around structured data, not summaries. Log pain points, trigger tasks, and link actions to the right next steps. If your AI output isn’t filling fields and creating motion, you’re just automating the wrong stuff faster.

Back to the top ⬆️

Why Tool Consolidation Fails Without Team Member Interviews

Landing in a new ops role and discovering 42 tools (some abandoned, some duplicated, some with logins no one remembers) is less a surprise and more a rite of passage. Everyone talks about cleaning it up, but few actually start from the right place. Kim doesn’t recommend audits or spreadsheets out of the gate. She recommends interviews. Real ones. With the humans who rely on those tools every day.

Your first job isn’t to eliminate waste. It’s to understand how people work. Ask questions like:

• What do you actually use?
• What problem does this tool solve for you?
• Where are you still doing things manually?
• If this tool disappeared tomorrow, would you care?

You are not just supporting marketing. You are supporting sales, CS, and sometimes operations across the board. Especially in orgs where marketing ops becomes the de facto expert on every system connected to the CRM. It’s easy to forget how many people duct tape their workflow around one feature inside one tool. Miss that, and you kill trust. Catch it early, and you build leverage.

“A lot of marketing ops folks are supporting way more than just marketing, especially if they’re the ones who actually understand the CRM.”

Once you understand the real behaviors, then you look for overlap. If three different teams use three different scheduling tools, choose the one people like most and help the others migrate. If sales is duplicating data entry across two platforms, consolidate. Not with a sledgehammer, but with empathy, context, and clear wins.

Key takeaway: Start with conversations, not audits. Talk to the teams, learn how they actually work, and earn the trust to start removing the noise. Tool consolidation works best when it’s based on behavior patterns and gaps, not what looks redundant on a spreadsheet. Your job isn’t to clean up software. It’s to reduce friction across the entire system without making things worse.

Back to the top ⬆️

Reframe Tool FOMO by Setting Clear Priorities and Capturing Curiosity

Every ops person knows the moment. Someone drops a link in Slack to a Chrome extension that “completely transforms onboarding” or a shiny new AI plugin that promises to 10x efficiency. The thread lights up. People get excited. And there you are, the person with the spreadsheet and the roadmap, saying, “Cool, but we don’t need this right now.” You’re not shutting it down. You’re redirecting attention to the things that actually matter.

Kim has seen this play out in real time. The tension isn’t in evaluating the tool. The tension is in being the only person asking whether it solves a real problem today, or whether it’s a distraction dressed up as innovation. She calls it out plainly. Ops isn’t just another stakeholder. It’s the only team that understands how sales, marketing, and success are stitched together. That perspective gives you the context to decide if a tool fits, or if it’s going to waste time and wreck clean data.

“If you’re in ops, you probably know more about what every team is doing than the teams themselves,” Kim said. “So it’s on you to understand what people care about and remind them what we’re actually working toward.”

The other problem runs deeper. Sometimes ops isn’t even in the room when tooling decisions are made. A new VP shows up, decides to bring in their favorite tool from a past role, and ops is looped in after the contract is nearly signed. No audits. No context. Just a directive. And now you’re duct-taping together a stack that nobody asked for, replacing a system that wasn’t broken.

That happens because the best ops work goes unnoticed. No bugs, no delays, no drama—so people forget you were behind the scenes holding it all together. Kim’s been through it. A sales rep once left her out of a rollout because he thought she was too busy to be bothered. His intentions were kind, but the result was a mess. If you don’t explicitly tell people where you need to be involved, they’ll assume it’s fine to move without you. Visibility takes repetition. 

That means:

• Sharing wins regularly
• Showing where you save time and reduce friction
• Defining the exact moments you should be brought in
• Explaining how you improve outcomes when you’re consulted early

You don’t need to kill tool curiosity. Just set the terms. Keep a doc of “interesting but not now” vendors. Reframe the conversation from tool FOMO to focus. When you do say no, make it clear what you’re prioritizing and why. Connect it to real goals and real pain points. Nobody wants another platform shelfed in month two.

Key takeaway: If you work in ops, your job is to protect the roadmap and your team’s time. That means saying no to the wrong tools and fighting for a seat at the table before decisions get made. Share your value, define your lane, and speak up often. That way you can stop cleanups before they start and keep your systems focused on what actually drives progress.

Back to the top ⬆️

Driving AI Tool Adoption Through User-Led Trust

Tool adoption fails when ops teams forget to think like end users. Kim sees this constantly—tools launched with polished internal decks, clever automation, and zero relevance to how anyone actually works. In theory, the tool solves a pain point. In practice, no one touches it.

She points out a pattern that’s easy to miss when you’re too close to the problem. Operators obsess over setup. Workflows, access, security, training materials. But users don’t care about frameworks. They care about whether this new tab in their browser actually makes their day smoother. Most teams are already running on fumes. If a tool doesn’t earn its keep in the first few uses, it just becomes more noise.

“People are busy. They don’t feel like they have time to learn a new tool,” Kim said. “You can’t push something from ops and expect adoption. You have to think about what someone’s day actually looks like.”

To make adoption real, you need three things:

• You need to know the current behavior. What are people actually doing right now?
• You need internal messaging that feels like peer-to-peer sharing, not top-down process enforcement.
• You need early adopters to act as quiet champions. Lunch-and-learns from a peer go further than any ops-led rollout call.

The moment a rep says, “I used this and now I don’t have to do XYZ manually anymore,” you’re in. That’s a win that others can see and believe. Internal trust spreads faster than enablement docs ever will. Ops can design the system, but adoption runs on reputation. Especially with AI tools, where skepticism is high and promised value rarely matches real usage.

Key takeaway: Tool adoption lives or dies on peer credibility. Learn the current workflow, find champions who actually use the tool, and let them tell the story. That way you can turn rollout resistance into real momentum.

Back to the top ⬆️

How to Build AI Skills If You Feel Like You’re Falling Behind

Many mid-career operators are quietly spiraling. They’re great at their jobs, deeply familiar with how things run, and then they see job descriptions asking for “LLM chaining,” “agentic workflows,” and “prompt engineering.” The work they’re already doing feels invisible next to a glossary of AI buzzwords that weren’t on the radar twelve months ago. The panic is real. But Kim’s view? Start by getting your hands dirty in small, tangible ways.

She suggests a daily practice with tools like ChatGPT or Claude. Not reading articles about them. Not watching conference panels. Just using them. Write your grocery list. Rewrite an email. Take something that already exists in your day-to-day and test how AI might assist. No special use case needed. Daily use creates familiarity, and that’s the baseline you’ll need before any of this feels like more than a gimmick.

“Even if it’s personal stuff,” Kim said, “just pick one thing and make it part of your workflow.”

A second move she recommends is counterintuitive: spend more time on LinkedIn. Yes, the content can be smug, repetitive, and full of recycled thought leadership. But that’s where people are posting real, messy examples of how they’re trying to use AI at work. It’s also where you’ll see what *not* to do. Watch what flops, learn what sticks, and take notes from the folks who are building with intention rather than hype-chasing.

From there, start asking around. Find someone on your team who seems to be using AI in interesting ways and ask them what they’re doing. Most people don’t feel like experts and will actually be thrilled you asked. Kim talked about a simple Relay App workflow they built—just pulling CRM notes and sending a Slack summary before a meeting. Nothing fancy. Just useful. There are dozens of these tiny bottlenecks in your day already. Once you find one, try fixing it with AI. Then do it again.

And there’s also courses. A few years ago, there weren’t many high-quality courses on using AI in marketing and SEO. That’s changed fast. Now, smart, credible folks are building solid educational content based on real experience. One example is Brittany Mueller, a former SEO scientist at Moz, who was early to machine learning and has since gone deep into AI. She created a course on Maven called Actionable AI for Marketers, which focuses on practical skills, especially for SEO professionals. People in the industry, including the speaker, have seriously considered taking it. The bottom line is that AI education for marketers has leveled up quickly thanks to people who actually know what they’re doing.

Key takeaway: Build AI fluency by doing, not just researching. Use ChatGPT or Claude daily in low-stakes tasks. Lurk on LinkedIn for real-world examples. Ask your coworkers how they’re automating tasks. Start small with tools like Relay or Zapier to design basic automations around real problems you face. That way you can build familiarity and momentum without waiting for a promotion, a budget, or a new job description to catch up.

Back to the top ⬆️

Why Generalists Are Thriving in the Age of AI

Most ops folks didn’t start in ops. They got there by circling through onboarding, customer success, partnerships, maybe a stint in product or design. That career path used to feel messy, like you were doing something wrong for not specializing. But Kim sees the opposite. She says those detours are the reason she’s good at her job.

She used to worry about being a generalist. Two years ago, she seriously considered going deep in a single discipline just to feel more legit. But with everything happening in AI and automation, she’s relieved she didn’t. “We’re seeing the rise of the generalist,” Kim said. “Someone who can think strategically across a bunch of areas and implement the right processes to make things more efficient.”

“We are going to see more lean and efficient teams,” she said. “And people with experience across multiple parts of the business are going to be a huge asset.”

It makes sense. AI is compressing execution. What used to take three people and a week of meetings can now be tackled by one person and a few prompts. That kind of environment rewards people who can move between functions, understand the upstream and downstream impacts, and rewire workflows without breaking everything. Generalists can do that. Specialists often can’t.

And this doesn’t mean staying broad at the expense of technical depth. The strongest ops folks are developing a working knowledge of AI while keeping their panoramic view of the business intact. That way they can spot patterns, reroute priorities, and actually ship changes that stick. Generalists with AI fluency are about to become the connective tissue of every high-output ops team.

Key takeaway: A wide-angle understanding of how departments operate, paired with emerging AI skills, is becoming one of the most valuable combinations in SaaS. Ops professionals who have jumped between roles should lean into that range, not hide it. You don’t need to pick a lane to be effective. You need to know how traffic flows across all of them.

Back to the top ⬆️

What Actually Keeps You Energized at Work Isn’t Balance

Balance gets all the headlines, but most people chasing it are already doing work they don’t enjoy. Kim admitted she made it her New Year’s resolution, but by spring, the idea had already collapsed. Not because she was drowning, but because she was genuinely energized. She spends her days at Arrows jumping between functions, solving hard problems, and doing work that actually matters to the business. That clarity makes long hours feel like momentum instead of a burden.

The signal is easy to miss. You don’t need a sabbatical or a better calendar template. You need a reason to care. Kim found hers in a role where she can clearly see how her effort moves the company forward. When you can say, “I shipped something today that helped us grow,” the tiredness feels earned. That kind of feedback loop doesn’t show up on a work-life balance infographic, but it makes all the difference.

Her joy isn’t theoretical. It’s rooted in context: early-stage startup, lean team, real autonomy. Kim isn’t sitting through stakeholder review cycles wondering what her job even is. She’s in the guts of the company, handling onboarding, internal operations, customer journeys, and product experiments, all before lunch. She’s not just filling a role, she’s moving pieces across the board.

What makes that sustainable is recognition. Not just public Slack shoutouts or manager 1:1s. Real-time signals that the work is seen, that it connects to outcomes, and that her fingerprints are on wins that matter. Kim pointed out that in jobs where she felt invisible, it wasn’t burnout that drove her out. It was feeling like nothing she did really mattered.

“If I feel like I’m doing valuable work and being recognized for it, I think that is the best setup you can have.”

You can’t fake that. And you can’t build it with a better morning routine. You have to find work that lets you contribute meaningfully and makes that contribution visible. That’s the foundation.

Key takeaway: Instead of chasing abstract balance, focus on doing work where your impact is clear and acknowledged. Energy comes from progress, not from avoiding exhaustion. If your job doesn’t give you a sense of contribution and recognition, no amount of mindfulness or time blocking will make it better.

Back to the top ⬆️

Episode Recap

Tool consolidation keeps getting pitched like spring cleaning your messy garage. Just run an audit, tally up features, cut the overlap. But in practice, that almost always backfires. The tools don’t live in a spreadsheet, they live in the weird, messy habits of actual humans doing actual work. People use three different apps to do one thing because each one solves a slightly different pain. If you skip the part where you talk to them, really ask how and *why* they’re working the way they are, you risk pulling the rug out from under systems that were already fragile. You might think you’re removing bloat but you might be breaking flow.

The folks who catch this early usually sit in ops. And the ones who are really good at it don’t wait until things go sideways to get involved. They’re already in the room, or they are knocking. They already know what every team is trying to hit this quarter. They’ve earned the trust to ask annoying questions and veto bad decisions before a contract gets signed. Because they’re the only ones looking at the whole system, not because they want to be grumpy blockers. Their job is to protect momentum. That means choosing slower starts over long cleanups.

Adoption doesn’t happen through rollout plans. It happens through people. One person makes their day easier with a new tool. They show someone else. That person tries it. Now it’s a thing. You don’t need to convince the whole company. You need two people who others actually listen to. That’s the part people skip. They write the playbook before they find their champion. But trust travels fast when it’s real.

Building that trust with AI takes practice. Not big dramatic workflows. Just small, boring reps. You open ChatGPT to draft an outline. You make a Zap that turns a Slack emoji into a ticket. You ask a coworker how they automated something you keep doing manually. It’s the kind of fluency that builds in the background, then suddenly becomes obvious. One day you realize you’re solving actual business problems without asking anyone for budget or permission. It just clicks.

And here’s where generalists shine. The people who’ve moved between sales, ops, product, and back again. The ones who can spot a workflow issue hiding in a reporting request. That range used to make it hard to define a role. Now it’s the edge. When AI starts creating leverage across every department, the people who already understand how those departments connect are going to move fast. They’re the ones who can design better workflows because they don’t just know the job. They know the traffic pattern.

All of this gets easier when you stop chasing the perfect setup and start focusing on the real, human work. Who’s stuck. What’s slow. What’s getting done twice. That’s the raw material. Everything else is just stack noise.

Listen to the full episode ⬇️ or Back to the top ⬆️

Follow Kim 👇

• LinkedIn
• Arrows.to

✌️

—
Intro music by Wowa via Unminus
Cover art created with Midjourney (check out how)

Apple •Spotify• Pocket Casts •Youtube •Overcast •RSS

Related tags

See all episodes

Future-proofing the humans behind the tech

Apple •Pocket Casts•Google •Overcast •Spotify •Breaker •Castro •RSS

• LinkedIn
• Twitter
• Instagram
• YouTube
• RSS Feed