Meetings Donโt Have to Suck

๐ **Source:** [Meetings Donโt Have to Suck](https://www.youtube.com/watch?v=pO_4ixp8s9Q#transcript)
> [!note]+ Document Notes
> ---
> tags: [eos-meeting-agenda, agency-management, sales-mentality, tyranny-of-the-urgent, freelance-networking]
> author: Kurt & Toby
> source: Agency Action
> reference: https://www.youtube.com/watch?v=pO_4ixp8s9Q
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
> ---
> # ๐ท๏ธ Title: Meetings Don't Have to Suck
> ## ๐งญ Table of Contents
> - [๐ Summary](#-summary)
> - [๐ Main Content](#-main-content)
> - [๐๏ธ Notes](#๏ธ-notes)
> - [๐ References](#-references)
> - [๐ฃ๏ธ Paraphrase](#๏ธ-paraphrase)
> - [๐ฐ Newsletter](#-newsletter)
> - [โ
Action Items](#-action-items)
> - [๐งช Hypotheses](#-hypotheses)
> - [๐ Methodology](#-methodology)
> - [โ Questions](#-questions)
> - [๐ฎ Future Research](#-future-research)
> - [๐ก Implications](#-implications)
> - [๐ง Learning Styles Assessment](#-learning-styles-assessment)
> - [๐ Accessibility Assessment](#-accessibility-assessment)
> - [๐ DEIB Assessment](#-deib-assessment)
> - [โ
Logical Validity](#-logical-validity)
> - [๐ก๏ธ DARVO Analysis](#-darvo-analysis)
> - [๐ฏ Conclusion](#-conclusion)
> ## ๐ Summary
> - Two agency owners, Kurt and Toby, unpack why they've historically hated meetings and how Toby is rolling out an EOS-style (Entrepreneurial Operating System) meeting agenda across his team: fixed time slot, fixed structure, hard stop, ranked issues list, and a running accountability list of to-dos.
> - It matters because both hosts run small agencies where meeting time is billable/opportunity cost, and unstructured meetings were producing status confusion (different team members reporting a project as "great" vs. "off the rails") and eroding trust in recurring 1:1s and standups.
> - Key stakeholders: agency owners and their ops/SEO/project-management teams; by extension, freelance clients who request recurring check-in calls; a hypothetical solo freelancer trying to build a client base from zero.
> - Risks and tradeoffs discussed: a rigid, issue-first agenda can let two people dominate the whole meeting on one topic; pure 1:1-only meeting structures (Kurt's dealership/Suzuki model) can hide problems that only surface when the full team compares notes together; "well poisoning" by chronically negative employees is hard to detect early and expensive to leave unaddressed.
> - Bottom line: a written, repeatable agenda with a triage mechanism for tangents, plus explicit issue-ranking and to-do ownership, is what converts a meeting from "information exchange nobody asked for" into "action tied to a decision."
> ## ๐ Main Content
> The episode opens with Kurt admitting he dislikes attending and running meetings, which sends him into researching what makes a meeting good. He lands on EOS (Entrepreneurial Operating System), a business-consultancy methodology with its own prescribed meeting agenda and philosophy, and Toby says he is actively rolling that agenda out across every recurring meeting at his agency (the Mighty Mo) โ starting with his weekly meetings with ops and SEO, and between ops and project management.
> The EOS format, as the hosts describe it: same day and time every week, a recommended 90-minute block (adjustable), an identical agenda every time, and โ critically โ the meeting always ends on time. Toby singles out chronic overrun as one of his core reasons for disliking meetings ("Ah, really? Now I'm late for the next meeting"). After running his first two EOS-format meetings, he reports getting through more material in less time than the old format typically took, even without allocating extra time to introduce the new template.
> Kurt frames the EOS agenda's core value as pre-defining "important" before the meeting starts, then ranking issues by that definition, so meeting time is spent solving the top-ranked issue rather than merely reporting status. He also raises an open problem the format doesn't fully solve: nothing stops two people from monopolizing the entire meeting on a single high-priority issue, since EOS's rule is "work the top issue until it's resolved or time runs out."
> Kurt contrasts this with his own management background at Suzuki, where he ran a 1:1-heavy model: dedicated meetings with specific individuals for specific work items (an e-learning module with one person, a service-manual edit with another) rather than pulling the whole team into narrow-scope discussions. Team-wide meetings, in his model, exist to broadcast what every stakeholder is doing โ sprint/Gantt-style status โ while the granular work happens in 1:1s.
> Toby pushes back with a concrete failure mode of the pure-1:1 model: he's recently gotten conflicting status reports on the same project from different team members in separate 1:1 conversations ("it's going great" vs. "it's going off the rails"), and believes a shared team meeting would have surfaced that discrepancy immediately. Kurt concedes the point using his own Lifter LMS example โ a live product announcement in a team meeting drew immediate stakeholder feedback ("we wanted X, Y, Z too") that reshaped the final feature โ while noting that off-topic-but-real feedback threads move to a side channel (Slack) rather than consuming the whole meeting.
> Toby extends this into a specific mechanic he used in his first EOS meetings: when a tangent surfaces mid-discussion, he acknowledges it, parks it at the bottom of the issues list, and only returns to it if time remains โ otherwise it's handled another way. He connects this to a broader triage failure most businesses have: "perceived emergencies push everything down" with no formal mechanism to check whether the emergency actually outranks existing priorities. He credits a short book, *Tyranny of the Urgent*, read for an unspecified prior study program (circa 2007โ2008), for reframing this: businesses that succeed protect time for what's important rather than reactively serving whatever feels urgent โ the origin, he says, of a time-blocking practice he and Kurt had discussed in a prior episode.
> A second accountability mechanic in the EOS format: each issue discussion converts into an owned to-do with a roughly week-to-week-or-per-cadence deadline, written down and visible to the whole group; if it isn't done by the next meeting, it re-enters the meeting as an issue. Toby names this as filling a gap his team previously had โ commitments made in meetings sometimes got lost with no forcing function to catch it.
> The conversation pivots to a related failure mode: negative or disengaged team members ("well poisoning") who can erode team morale quickly, sometimes invisibly, and the risk that a single badly-run rollout of a new process can permanently sour a team on it. Kurt shares an anecdote about an employee at a client company who volunteers unprompted complaints about the business to an outside contractor (Kurt himself), and the hosts agree this kind of chronic negativity likely does measurable damage even when it's hard to quantify.
> The second half of the episode is a hypothetical exercise: if dropped into an unfamiliar city with $200, a laptop, and no ability to use prior contacts or their real name, how would Kurt and Toby (as freelance WordPress developers) find work from zero? Their answers converge on: find city/county-subsidized small-business or economic-development programs (free enrollment as a "student" gets you into a room with other founders who need websites); use free-to-cheap first jobs to "break the ice" and build referral relationships, including with nominal competitors; show up consistently and specifically at any venue with the right people and energy (co-working spaces, gyms, meetups, libraries with WiFi); do targeted homework on attendees before events; be a "good host" by connecting other people at events, at no cost to yourself; and build relationships by transacting as a customer first (buying a coffee, a bike tube) to open a natural, low-pressure conversation.
> Both hosts land hard on a sales-before-marketing sequencing: build a minimal, credible offer only once you have a live prospect asking for it (a website mocked up after a conversation, not before), and prioritize revenue-generating conversations over branding, tooling experimentation, or "vibe coding" side projects. Toby explicitly contrasts this with the temptation to chase "the top of everything" (new AI tools, new page builders) when the actual leverage for most agencies is a small, boring WordPress plugin stack executed consistently and paired with a strong sales mentality.
> ### ๐๏ธ Notes
> - EOS meeting mechanics named on the show: fixed weekly slot, ~90-minute default, identical agenda each time, hard stop, pre-ranked issues list, tangent-parking, and a persistent to-do/accountability list reviewed each meeting.
> - EOS does not, per Kurt, solve for two people monopolizing an entire meeting on one high-priority issue โ an acknowledged open gap in the format as they're using it.
> - Kurt's Suzuki-era rule of thumb: narrow-scope work items get a dedicated 1:1 meeting with the specific stakeholder; team meetings are for status/education, not detailed problem-solving.
> - Counter-case from Toby: 1:1-siloed status reporting produced contradictory answers about the same project's health from different team members โ a failure the team-meeting format is structurally better at catching.
> - Lifter LMS example (Toby, customer-service team member) โ Chris Badgett unveiled the in-development "events add-on" in a team meeting; Brian (developer) and Toby debated scope live, then moved details to Slack; the shipped feature matched the feedback surfaced in that meeting.
> - "Perceived emergencies push everything down" โ named as a triage gap most businesses lack tooling for; *Tyranny of the Urgent* (short book, read circa 2007โ2008 for an unnamed required-reading program) is credited as the source that reframed this for Kurt and, indirectly, seeded a time-blocking habit referenced from a prior episode.
> - To-do accountability loop: issue discussion โ owned to-do โ deadline (roughly weekly/meeting-cadence) โ reviewed next meeting as done/not-done โ not-done reopens as an issue.
> - "Well poisoning": a single chronically negative employee, per Kurt and Toby, can measurably (if hard to quantify) damage morale and even client-facing service quality; the hosts note this is hard to catch early because new hires naturally cycle through a competence/confidence ramp that can look similar on the surface.
> - Toby: "one bad experience as you roll something out internally can ruin it forever" โ process-change adoption risk tied to first-run execution quality, not just the process design itself.
> - Freelance-from-zero mechanics named: subsidized economic-development/small-business programs as a client and peer-network source; competitor referrals for out-of-niche work; co-working-space front-desk staff as connectors; "buy something small first" to open a relationship (explicitly borrowed from *American Pickers*-style dealmaking); do-the-website-after-the-conversation, not before.
> - Explicit sales-vs-marketing framing: sales/revenue-first sequencing, marketing and tooling experimentation deferred until there's a live customer relationship to build around; named as a callback to a "marketing vs. sales" disagreement from the prior week's episode.
> - Toby's closing point: a small, standard WordPress plugin stack is sufficient to run "an entirely profitable agency" โ framed as a corrective to distraction-by-tooling (page builders, AI experimentation) rather than a technical claim about plugin choice.
> ## ๐ References
> - [EOS Worldwide โ Entrepreneurial Operating System](https://www.eosworldwide.com/) โ the methodology and meeting-agenda template Toby is rolling out (named directly in the transcript; not independently verified against this exact URL).
> - *Tyranny of the Urgent*, Charles E. Hummel โ short book Toby credits for reframing urgent-vs-important triage and time-blocking.
> - [Lifter LMS](https://lifterlms.com/) โ Chris Badget[t], cited by Kurt as a model for well-run team meetings and as the source of the events-add-on example.
> - Maรฑana [agency name as transcribed; exact spelling unconfirmed from audio] โ Kurt's agency.
> - tmigtm.com [as transcribed; likely "TMI-GTM.com"] โ Toby's agency, "the Mighty Mo."
> ## ๐ฃ๏ธ Paraphrase
> - Kurt didn't set out to research meeting design โ he set out to stop hating meetings, and that search led him to EOS's specific, repeatable agenda template as one candidate answer, which Toby is now testing live across his team's recurring meetings with early positive signal (shorter meetings, more covered) after only two runs.
> - Both hosts converge on a shared diagnosis for why meetings fail โ no agenda, unclear purpose, wrong attendees, no ending discipline, no accountability trail โ and on a shared prescription that isn't really about tooling: pick a structure, protect it from scope creep with a parking mechanism, and force every discussion to end in an owned commitment.
> ## ๐ฐ Newsletter
> Tired of meetings that run long, wander off-topic, and evaporate into nothing by next week? This episode of Agency Action has Kurt and Toby field-testing the EOS meeting agenda live โ same slot, same structure, hard stop, ranked issues, and a to-do list that actually gets checked next time. Bonus: a fun "drop me in a new city with $200" thought experiment on rebuilding a freelance client base from zero, heavy on relationship-first, sales-before-marketing thinking. Recommended if you run โ or dread โ a recurring team meeting.
> ## โ
Action Items
> Most standard action-item categories in this template (DevRel, OSPO, WPCC, FAIR) don't map cleanly to this episode's content, which is general small-agency operations rather than open-source or WordPress-project governance. The categories below are the ones the transcript actually supports.
> #### WordPress โ Community
> - Maintainers: the EOS-style fixed-agenda-plus-issues-list-plus-accountability-loop format discussed here is a reusable template for any recurring maintainer sync (roadmap clinics, release-team standups) โ worth trialing on a small recurring meeting to see if it reduces overrun and improves follow-through on action items.
> #### General agency/business operations (outside standard taxonomy)
> - Pilot a fixed-agenda, hard-stop meeting format (EOS-style or equivalent) on one recurring internal meeting; track whether issues get resolved faster and whether to-dos get closed by the next cycle.
> - Build a lightweight parking-list mechanic for tangents in any standing meeting, so real-but-off-topic items get captured without derailing the agenda.
> - If running or considering client check-in calls, audit whether they're solving something a client portal/status page couldn't โ per Toby's point that many recurring client meetings are an "emotional security blanket" better addressed by proactive, self-serve status transparency.
> ## ๐งช Hypotheses
> - H1: Adding a hard time-stop and a pre-ranked issues list to a recurring meeting reduces total meeting time while increasing the number of resolved issues per meeting.
> - H2: Meetings run purely as 1:1s between a manager and individual contributors under-surface cross-functional status discrepancies compared to a shared team meeting covering the same work.
> - H3: A visible, reviewed-every-cycle to-do/accountability list increases the rate at which meeting-generated commitments are completed by the next meeting, relative to commitments made without such a list.
> - H4: For early-stage freelancers/agencies, revenue generated through direct relationship-building (in-person networking, competitor referrals, subsidized small-business programs) outweighs revenue attributable to marketing/branding investment in the first months of operation.
> - H5: A single consistently negative team member measurably reduces team morale or client-facing service quality over time, independent of that person's individual output quality.
> ### ๐ Methodology
> - H1: A/B or before/after comparison of the same recurring meeting series (EOS-style agenda vs. prior ad hoc format), tracking meeting duration, number of issues resolved, and participant-reported satisfaction over 8โ12 weeks.
> - H2: Compare status accuracy (self-reported vs. independently verified project state) collected via 1:1s only vs. collected via a shared team meeting, across matched teams or alternating formats on the same team.
> - H3: Track completion rate of meeting-generated to-dos with vs. without a persistent, reviewed accountability list, controlled for task type and owner.
> - H4: Time-series revenue attribution study for early-stage freelancers, comparing revenue sourced from direct relationship channels vs. paid/organic marketing channels in the first 90 days.
> - H5: Team-morale survey (e.g., eNPS or a validated short instrument) correlated with presence/tenure of a chronically negative team member, controlled for team size and workload.
> ### โ Questions
> - What specific triage rule resolves the case Kurt raised โ two people legitimately needing the entire meeting for one top-priority issue โ without either derailing the group agenda or starving the issue of needed time?
> - How does the EOS format's fixed 90-minute default scale down for smaller teams (2 people, as in Toby's first two runs) versus larger cross-functional groups?
> - What's the actual failure rate of "emotional security blanket" client check-in calls when replaced by proactive self-serve status tooling โ does client anxiety measurably drop, or does it surface elsewhere?
> - Is there a reliable early-warning signal for "well poisoning" that's distinguishable from normal new-hire ramp-up friction?
> ### ๐ฎ Future Research
> - A structured comparison of EOS's Level 10 meeting format against other named meeting operating systems (e.g., Scrum standups, Amazon's narrative-memo meetings) on time-to-resolution and follow-through metrics.
> - Longitudinal tracking of Toby's team-meeting rollout at the Mighty Mo to see whether the early positive signal (two meetings) holds past the "discipline decay" risk both hosts flagged.
> ### ๐ก Implications
> - For practice: teams frustrated by long, low-output meetings have a low-cost experiment available (fixed agenda + hard stop + parking list + accountability review) that doesn't require new tooling to trial.
> - For policy/governance in maintainer or community teams: the same mechanics could reduce volunteer burnout tied to open-ended, poorly bounded recurring calls.
> - For freelance/agency education: the "drop into a new city" exercise implies most practical go-to-market advice for solo freelancers is relationship-sequencing advice, not marketing-channel advice โ a useful framing for mentorship or onboarding content aimed at new freelancers.
> ### ๐ง Learning Styles Assessment
> - Reading level estimate: conversational spoken-word transcript; approximate Flesch-Kincaid Grade Level ~6โ8 (short average sentence length once filler and false starts are normalized, informal vocabulary, minimal subordinate-clause density). Note this is an estimate from a raw transcript, not a cleaned written text.
> #### ๐ Visual learners
> - Present: none โ audio-only podcast transcript, no diagrams, charts, or visual aids.
> - Improve: a one-page visual of the EOS meeting agenda flow (issue list โ rank โ discuss โ to-do โ next-meeting review) would make the core structural claim far more scannable.
> #### ๐ Aural learners
> - Present: this is a native audio/podcast format โ well served by design.
> - Improve: chapter markers at the two clear topic breaks (meetings segment, freelance-from-zero segment) would help aural learners navigate on replay.
> #### ๐ฃ๏ธ Verbal learners
> - Present: concrete anecdotes (Suzuki, Lifter LMS, the bike-shop example) function as informal analogies throughout.
> - Improve: a short glossary of named terms (EOS, "well poisoning," "tyranny of the urgent") would help verbal learners anchor unfamiliar jargon introduced conversationally.
> #### ๐งฉ Kinesthetic learners
> - Present: the episode implicitly offers a testable template (the EOS agenda) that a listener could try immediately.
> - Improve: an explicit step-by-step checklist for running one's first EOS-format meeting, extracted from the conversation, would convert this into a usable lab exercise.
> #### ๐ง Logical learners
> - Present: Kurt and Toby build several explicit cause-effect chains (no agenda โ overrun โ late for next meeting โ resentment of meetings).
> - Improve: a simple decision tree for "1:1 vs. team meeting" based on the scope-of-impact question Kurt and Toby debate would formalize their implicit heuristic.
> #### ๐งโ๐คโ๐ง Social learners
> - Present: the whole episode is a two-person dialogue model, useful as a discussion-prompt format.
> - Improve: discussion questions derived from the "well poisoning" segment could seed a peer support-group or mastermind conversation.
> #### ๐งโโ๏ธ Solitary learners
> - Present: none explicitly โ no reflection prompts or self-assessment offered in the source.
> - Improve: a short self-audit ("does your last recurring meeting have a written agenda? does it end on time? do to-dos get reviewed?") would give solitary learners a self-paced entry point.
> #### ๐ฟ Naturalistic learners
> - Present: not applicable to this content.
> - Improve: not applicable.
> ### ๐ Accessibility Assessment
> This assessment covers the transcript as a text artifact, not a rendered video player.
> #### Screen reader semantics
> - Present: this note's own heading structure gives the transcript navigable landmarks it lacks in raw form.
> - Improve: if published as an Obsidian note, keep heading hierarchy intact (already applied here) so a screen reader user can jump by section.
> #### Keyboard navigation
> - Not applicable to a transcript/note; applies to the video player, not assessed here.
> #### Contrast and readability
> - Not applicable to plain-text transcript content.
> #### Text resizing and reflow
> - Not applicable to plain-text transcript content.
> #### Media and captions
> - Present: a transcript exists, which functions as an accessible alternative to the audio/video.
> - Improve: no timestamps are present in the source transcript, so this note cannot offer deep-linked, timestamped citations (see Transcript Mode note below) โ the original video should carry accurate closed captions and, ideally, a timestamped transcript for that purpose.
> #### Forms and interactions
> - Not applicable โ no interactive elements in this content.
> #### Standards reference
> - Primary gap relative to WCAG 2.2 AA: absence of timestamps in the source transcript limits deep-link accessibility (1.2.x media-alternative criteria) for anyone trying to verify or navigate to a specific claim in the original video.
> ### ๐ DEIB Assessment
> #### Cultural breadth
> - Present: examples are drawn from a narrow set of US small-business contexts (car dealerships, Suzuki corporate, a Kansas/New Mexico economic-development framing).
> - Improve: the freelance-from-zero advice (subsidized small-business programs, co-working spaces) assumes US-style municipal/county economic-development infrastructure; equivalent advice for other regulatory or economic contexts is absent.
> #### Inclusive language
> - Present: informal but not exclusionary language throughout; no notable jargon barriers beyond business-consultancy terms (EOS) that are defined in context.
> - Improve: a brief inline definition of "EOS" on first use would help listeners unfamiliar with the consultancy space.
> #### Neurodiversity support
> - Present: the episode's own subject matter (structured agendas, hard stops, written accountability) is itself a neurodiversity-friendly meeting practice, even though it isn't framed that way.
> - Improve: explicitly naming the accessibility/neurodiversity benefit of predictable, agenda-bound meetings would strengthen the pitch for adopting the format.
> #### Representation
> - Present: two male hosts, generalist small-business examples; no notable diversity of speaker identity within this episode.
> - Improve: broader speaker representation in future episodes covering the same topic would diversify perspective on team dynamics like "well poisoning."
> #### Psychological safety
> - Present: the "well poisoning" segment discusses identifying and ultimately terminating chronically negative employees without addressing root-cause support (e.g., burnout, misalignment, management failure) before jumping to "liquidate."
> - Improve: pairing the well-poisoning discussion with a root-cause diagnostic step (is this a fit problem, a burnout problem, or a management problem?) before termination would improve psychological safety for the broader team and fairness to the individual involved.
> ### โ
Logical Validity
> #### Strong reasoning
> - Kurt's argument for scoped 1:1 meetings (Suzuki example) is a clear causal/analogical argument: matching meeting composition to the actual stakeholders of a decision reduces wasted attendee time โ directly addresses his own earlier complaint about being in rooms "for two people and a dude."
> - Toby's counter-example (conflicting project-status reports across 1:1s) is inductive reasoning from a specific recent pattern to a general claim about the limits of 1:1-only structures โ reasonably strong because it's a falsifiable, recent, first-hand observation rather than a hypothetical.
> #### Fallacies
> - Toby's dad's advice ("join the priciest gym and show up every day" as a marketing plan) is offered and half-endorsed ("there's a lot of logic to that") on the strength of a single anecdote โ a hasty generalization; no evidence is offered that gym-based networking outperforms other venues for lead generation specifically. Fix: frame it as one illustrative example of "go where people with resources gather," not as a validated tactic.
> - The "billion-dollar WordPress boss" thought experiment reasons from a hypothetical, resource-constrained scenario to general freelance-acquisition advice; useful as illustration but risks false-analogy if generalized directly to real freelancers who typically retain some prior network. Fix: the hosts partly self-correct by grounding tactics in things they've actually done (Hutchinson, Kansas example), which strengthens the analogy.
> #### Tone of voice
> - Casual, self-deprecating, conversational; frequent hedging ("I think," "I don't know") signals genuine uncertainty rather than overclaiming, which is a credibility strength for an advice-format podcast.
> ### ๐ก๏ธ DARVO Analysis
> Not applicable โ this episode contains no accusation, denial, or victim/offender dynamic to analyze. It is a two-host advice conversation without an adversarial or accountability-dispute structure.
> ## ๐ฏ Conclusion
> The core, testable claim of this episode is narrow and practical: a fixed-time, fixed-agenda, hard-stop meeting format with a ranked issues list and a reviewed accountability trail measurably improves recurring meetings, at least on the two-meeting sample size Toby reports. The unresolved tension the hosts surface themselves โ team-wide meetings catch cross-functional status gaps that 1:1-only structures miss, but a rigid issues-first agenda can still let one topic swallow the whole meeting โ is the most useful open question for anyone adopting this format. Practical next step for readers: pick one recurring meeting, write a fixed agenda with a parking mechanism for tangents, add a to-do list reviewed at the start of the next meeting, and track whether it changes duration and follow-through before rolling it out further.
> ## ๐ Refactor Appendix โ Meetings Don't Have to Suck
> > Density: 2โ5 Literature atoms (H3), 0โ3 Permanent candidates (H4).
> > This source is a fresh transcript, not a pre-highlighted Readwise export โ no `rw_{id}` highlight IDs exist yet, so quotes below are direct verbatim transcript excerpts rather than Readwise-anchored highlights.
> ### ๐ Literature Atoms (H3)
> #### EOS meetings pair a fixed agenda with a hard stop
> > [!quote]
> > "same time every week... same agenda every meeting and it always ends on time."
> **Context & use**:
> - Toby describing the EOS meeting template he's rolling out at the Mighty Mo.
> - Matters because chronic overrun is named as one of the specific reasons meetings are hated; a hard stop directly targets that complaint.
> **Tags**: #xref
> <!-- atomicity: 1 idea โ -->
> #### Team meetings catch status gaps 1:1s hide
> > [!quote]
> > "I'm getting different answers from different people. Oh, it's going great... The next guy is like, no, it's going off the rails."
> **Context & use**:
> - Toby's counter-example to Kurt's 1:1-heavy Suzuki model.
> - Matters because it's the strongest concrete evidence in the episode against relying solely on individual check-ins for status visibility.
> **Tags**: #xref
> <!-- atomicity: 1 idea โ -->
> #### Perceived urgency crowds out actual priority without triage
> > [!quote]
> > "perceived emergencies push everything down but there's no... great triage system to say... let's think about where this emergency fits amongst our other priorities."
> **Context & use**:
> - Toby, connecting the meeting-agenda discussion to *Tyranny of the Urgent* and time-blocking.
> - Matters as the conceptual bridge between meeting hygiene and broader prioritization discipline.
> **Tags**: #xref #addendum
> <!-- atomicity: 1 idea โ -->
> ### ๐ง Permanent Candidates (H4)
> #### Meeting structure should match decision scope, not team size
> **Claim** (one sentence, in Courtney's voice): A recurring meeting's attendee list and agenda should be sized to the actual scope of the decision being made, not to organizational hierarchy or habit โ narrow decisions get a 1:1, cross-functional status needs a shared room, and the two failure modes (irrelevant attendees vs. hidden status gaps) are two sides of the same sizing mistake.
> **Evidence pointer**: [[#EOS meetings pair a fixed agenda with a hard stop]], [[#Team meetings catch status gaps 1:1s hide]]
> **Scope & conditions**:
> - Holds when: the team has enough shared context to make "scope of decision" legible in advance (i.e., someone can actually pre-rank what's important, as EOS requires).
> - Breaks when: status itself is contested or unknown โ in that case a 1:1-only structure can silently diverge (per Toby's example) and only a shared venue surfaces the conflict.
> **Links**:
> - [[Tyranny of the Urgent]] โ because extends (urgent/important triage is the upstream discipline this meeting-sizing rule depends on)
> - [[EOS meeting agenda]] โ because applies-in (the specific operational template tested in this episode)
> <!-- atomicity: 1 idea โ -->
> ### โ๏ธ Fleeting Queue
> - [F1] Look into EOS's Level 10 meeting template directly (primary source, not secondhand via this podcast) to compare against the version Kurt and Toby describe โ https://www.eosworldwide.com/ #xref
> - [F2] Track whether Toby reports back on this podcast in future episodes about whether the EOS rollout holds past the first few meetings (discipline-decay risk both hosts flagged) #xref
> ### โ Things 3 (max 2 actions)
> - [ ] Pilot a fixed-agenda, hard-stop format on one recurring meeting for two cycles and compare duration/resolved-issues to the prior format โ meeting-hygiene experiment #things
> - [ ] Read *Tyranny of the Urgent* (Charles Hummel) as a short primer on urgent-vs-important triage referenced in this episode โ reading backlog #things
> ---
> ## Full Transcript
> [00:00] Well, here we are again, folks. Welcome<br>[00:01] to another agency action show. I'm here<br>[00:04] with Toby Kines. My name is Kurt. Toby,<br>[00:07] talk to me about uh meetings and how<br>[00:09] much you love having meetings. I've<br>[00:11] realized um I really don't like having<br>[00:13] meetings and going to meetings and<br>[00:15] holding them. But then it got me<br>[00:16] thinking like what would a good meeting<br>[00:18] look like? And there's a whole like<br>[00:20] there are business consultancies and<br>[00:22] whole like a whole vertical of business<br>[00:24] consultancies that are focused almost<br>[00:26] exclusively on this topic. Um, and I was<br>[00:29] looking into one that's called EOS and<br>[00:31] um, there are others and I'm sure<br>[00:33] they're all fine in their own ways, but<br>[00:35] specifically I was looking at it from a<br>[00:37] meeting management standpoint and like<br>[00:39] what is a great meeting? How do you have<br>[00:40] a meeting where people leave the meeting<br>[00:42] and go, "Thank you. I'm glad we had that<br>[00:44] meeting." Even if you know in the book<br>[00:47] and the the philosophy of EOS that<br>[00:49] they're like, you want people to say<br>[00:50] it's a great meeting, but I'm not aiming<br>[00:52] for great. I'm aiming like great in the<br>[00:54] context of business meetings because<br>[00:56] nobody really wants to be in them.<br>[00:59] >> Um but and so then I got into it and I<br>[01:01] actually so EOS has a its own meeting<br>[01:04] agenda template and philosophy and I<br>[01:06] actually implemented I'm imple<br>[01:08] implementing this agenda at the mighty<br>[01:10] mo for any recurring meeting. So this is<br>[01:11] like weekly meetings between me and my<br>[01:13] operations team between me and my SEO<br>[01:16] team between operations team and project<br>[01:18] management team like we're implementing<br>[01:19] that we're rolling it out. We had our<br>[01:21] first two today and I got to say it's I<br>[01:25] felt way better about the meeting the<br>[01:28] meeting these two meetings today than I<br>[01:29] have about any previous one. And I think<br>[01:31] part of the philosophy behind the EOS<br>[01:33] thing is that uh every meeting has its<br>[01:36] same time every week. It's they<br>[01:38] recommend 90 minutes but um you know you<br>[01:40] can decide that I guess but uh same<br>[01:43] agenda every meeting and it always ends<br>[01:45] on time. And this is like a problem.<br>[01:47] This is part of why I hate meetings is<br>[01:49] because they're always going over and<br>[01:50] I'm always like, "Ah, really?" Like<br>[01:52] again, now I'm late for the next<br>[01:53] meeting. And so I did two today. And<br>[01:57] even though we didn't even plan enough<br>[01:59] time because like I was like, "I want to<br>[02:01] share this meeting template idea with<br>[02:02] you." Um the so the meetings were<br>[02:04] actually like in in context of that way<br>[02:06] shorter than they would have otherwise<br>[02:08] been and we still I felt like got<br>[02:10] through way more than we otherwise would<br>[02:12] have historically. So, wanted to ask<br>[02:15] you, Kurt, what are some reasons<br>[02:16] meetings suck in your experience?<br>[02:20] >> I think in general,<br>[02:23] when you say agenda, that that to me is<br>[02:25] like that's the lynch pin. That's that's<br>[02:27] the thing. Um, I've worked with a ton,<br>[02:31] you know, I have that corporate<br>[02:32] experience and I've worked for a lot of<br>[02:33] car dealerships and a lot of car<br>[02:35] dealerships aren't run by people that<br>[02:37] are leadership experts. They're run by<br>[02:39] people that are car enthusiasts. And so<br>[02:41] I know what bad meetings look like. Uh<br>[02:43] I've also had the privilege of I know<br>[02:46] this this everyone's going to think this<br>[02:47] guy owes me money. Chris Badget at<br>[02:49] Lifter LMS, I go to his meetings. He's<br>[02:51] like a master at running a good meeting.<br>[02:53] Um it's interactive. You know, what are<br>[02:56] our wins? What are our losses? What what<br>[02:58] are our key points? What are our focus<br>[03:00] points? And you know, what do we pin to<br>[03:02] talk about later? You know, one-on-one<br>[03:03] or something like that. I think one of<br>[03:05] the things that I hate about meetings is<br>[03:09] when you're in a room with 10 people and<br>[03:11] it seems like the meeting is for two<br>[03:13] people and a dude, you know, and you're<br>[03:15] sitting there like an idiot. Like I<br>[03:16] don't even know why I'm here. Like that<br>[03:18] for me is like these are not meetings I<br>[03:20] need to be in.<br>[03:21] >> Yeah. I think even with the EOS<br>[03:23] template, it doesn't solve that specific<br>[03:26] problem.<br>[03:27] Um what it does solve, however, is is<br>[03:30] let's work on the most important stuff.<br>[03:32] let's first define how do we define<br>[03:34] importance. So there's a lot of like<br>[03:36] pre-work you do um just to define from<br>[03:39] from the business standpoint what's<br>[03:40] important and then when you get to these<br>[03:42] meetings you go like okay we now have<br>[03:44] the context for how do we define<br>[03:45] important which are these items and then<br>[03:47] you rank them by the order of importance<br>[03:49] to the business and um and and the idea<br>[03:53] is like you're not spending a lot of<br>[03:55] time like talking about what you're<br>[03:56] doing but like solving the issues but I<br>[03:59] could still see a scenario where two<br>[04:00] people are going back and forth on a<br>[04:02] specific issue for a long period of<br>[04:04] time. It could be the whole meeting<br>[04:05] frankly because the way that EOS sets it<br>[04:07] up is like you have your most important<br>[04:09] thing first and you don't stop until<br>[04:11] either that issues done or the time for<br>[04:13] the meeting's done and and so you could<br>[04:15] potentially have two people talking the<br>[04:17] whole meeting and I yeah I don't know<br>[04:19] how you solved that.<br>[04:20] >> So so in those instances um and and I'll<br>[04:23] drive this back to my work at Suzuki,<br>[04:25] right? I was in charge of a group of six<br>[04:27] people that did all the publications and<br>[04:28] training for Suzuki. If I was concerned,<br>[04:31] if my number one priority was an<br>[04:34] e-learning module uh being done by<br>[04:36] Michelle, uh me and Michelle would book<br>[04:39] a room and have a meeting, right? Like<br>[04:40] like that would be the meeting and<br>[04:42] here's my agenda for the meeting with<br>[04:43] Michelle. I wouldn't bring, you know,<br>[04:46] Bill, Tristan, and Ron into the meeting<br>[04:47] with Michelle to talk about the<br>[04:49] e-learning module, right? Um if there<br>[04:51] was a uh something that had to be edited<br>[04:53] for a service manual, uh I would meet<br>[04:56] with Ron one-on-one, but I wouldn't<br>[04:57] bring in again the whole team, right?<br>[04:59] for those and that's why the agenda<br>[05:00] thing is so important because if I'm<br>[05:02] going to have a group meeting right what<br>[05:04] are the what are the top most important<br>[05:07] things that affect the group and then<br>[05:09] boom boom boom so I think when we have a<br>[05:12] team meeting and again I'm going to<br>[05:13] drive back to the lifter LMS example<br>[05:15] when we have a team meeting it's really<br>[05:18] to educate the team as to what all of<br>[05:20] the stakeholders are actively doing or<br>[05:22] or the process or the progress of things<br>[05:24] and so we'll take a look at like you<br>[05:26] know the the flowchart for sprints or<br>[05:28] the Gant chart or whatever you want to<br>[05:29] call it, right? So, development's<br>[05:31] working on this, sales is working on<br>[05:33] this, da da da da da, customer service<br>[05:36] is knocking it out of the park with<br>[05:37] these five things. Here's three new<br>[05:39] testimonials, sales is good, here's the<br>[05:41] the, you know, the bundles we sold this<br>[05:43] week. And then all of the details get<br>[05:46] handled in individual meetings for<br>[05:48] development with those individual<br>[05:50] stakeholders. I think I'm just guessing<br>[05:53] here maybe and from experience like that<br>[05:57] I've seen at the Mighty M where that<br>[05:59] model potentially has a shortcoming that<br>[06:01] would need to be addressed is often<br>[06:03] times the issues surface in these<br>[06:05] conversations with the team that the<br>[06:08] issues even though they're really<br>[06:09] important wouldn't otherwise surface.<br>[06:11] I'll give you an example. Um, recently<br>[06:14] I've been having these like one-off<br>[06:16] conversations with people on my team,<br>[06:18] like about a specific pro project and<br>[06:20] asking questions about how it's going.<br>[06:22] And I'm getting different answers from<br>[06:24] different people. Oh, it's going great.<br>[06:25] Going great. The next guy is like, no,<br>[06:26] it's going off the rails. And I'm like,<br>[06:30] um, I think if we had had a team meeting<br>[06:32] that would have surfaced and like, hey,<br>[06:33] how's it going? Going great. Sucks. Like<br>[06:35] it' be like going off the rails. Like<br>[06:37] like maybe<br>[06:38] >> I don't know. Yeah, I had to do a lot of<br>[06:41] leg work to get there. Yeah, I I do see<br>[06:43] your point. If we again using Lifter as<br>[06:45] the example because that's, you know, my<br>[06:47] my most recent experience. Um, Lifter<br>[06:49] just came out with the events add-on,<br>[06:52] right? So, you can do live Zoom events<br>[06:53] or inerson events attached to your<br>[06:56] website. And during one of those team<br>[06:58] meetings, Chris unveiled to the rest of<br>[07:01] us underlings that, you know, the this<br>[07:03] events add-on was going to come out. Now<br>[07:05] I work on the customer service team and<br>[07:06] so I'm responsible to like show it to<br>[07:08] people, you know, teach people how to<br>[07:10] use it and all that kind of stuff, but<br>[07:11] it was still in development. And Brian,<br>[07:13] the developer, was like, "Yeah, the<br>[07:14] events thing's kind of cool. It's going<br>[07:15] to XYZ." And I was like, "Whoa, whoa,<br>[07:17] whoa, hold on." Like the feedback we've<br>[07:18] gotten from stakeholders already is that<br>[07:20] we wanted to do X, Y, and Z in addition<br>[07:22] to what you just said. And then he goes,<br>[07:24] "Oh, that's a good idea." Right? But<br>[07:26] then we took that discussion to Slack<br>[07:29] for some details between him and I. And<br>[07:31] when they released the events package,<br>[07:33] it did exactly what I wanted it to do<br>[07:34] and Brian knocked it out of the park. So<br>[07:36] to your point, there there are things<br>[07:38] that come up, you know, through the<br>[07:40] agenda and through sharing things with<br>[07:41] the team. There are things there there's<br>[07:44] elements that come up, but we don't<br>[07:46] absorb the meeting with those things. We<br>[07:48] give the opportunity for fine-tuning<br>[07:50] outside that meeting.<br>[07:51] >> Yeah. I I also think one thing I noticed<br>[07:53] today in my two meetings that use the<br>[07:55] new EOS format. I noticed because I was<br>[07:58] in charge of leading the meetings and we<br>[08:00] have a firm schedule uh firm agenda and<br>[08:02] we have places to put things that like<br>[08:05] and this is just me and one other person<br>[08:07] in both meetings and I noticed they were<br>[08:09] either them or I were bringing up things<br>[08:11] that were tangential to what we were<br>[08:13] currently dealing with. Like we're<br>[08:14] talking about an issue and they say,<br>[08:16] "Well, what about this?" And it's like I<br>[08:17] can see how it relates. And it was<br>[08:19] really nice to be able to say like,<br>[08:20] "Thank you for sharing that. I'm going<br>[08:22] to put that at the bottom of the issues<br>[08:24] list and if we have time later today,<br>[08:25] we'll get to it. Otherwise, we'll deal<br>[08:27] with it a different way."<br>[08:28] >> It's like our show notes. [laughter]<br>[08:30] >> Yeah, it is. Yeah.<br>[08:32] >> Well, we'll drive these uh these crappy<br>[08:34] notes down to the bottom and if we run<br>[08:35] out of time, we'll talk about it.<br>[08:36] >> And I think the reality is is that like<br>[08:38] those tangential things probably weren't<br>[08:41] as important like first of all uh and<br>[08:43] probably they're, you know, they don't<br>[08:45] deserve to be injected at the top. And<br>[08:47] we notice this all the time like in our<br>[08:49] company that like perceived emergencies<br>[08:51] push everything down but there's no like<br>[08:53] we don't currently have like a great<br>[08:55] triage system to say like slow down<br>[08:57] let's think about where this emergency<br>[08:59] fits amongst our other priorities. And I<br>[09:02] think like this meeting agenda handles<br>[09:04] that for meetings. It doesn't handle it<br>[09:06] for our business necessarily but like<br>[09:07] that happens at meetings all the time<br>[09:09] where someone brings something up and in<br>[09:10] my view derails the whole conversation<br>[09:12] of whatever was being brought up or<br>[09:14] conversed about. That's so important<br>[09:16] from a business perspective. Um I was<br>[09:19] doing some um study I I I don't want to<br>[09:23] get why right but but one of the<br>[09:24] required readings for this study that I<br>[09:26] was in and I'm going back like I think<br>[09:28] it was 2007 or 8 um was a little tiny<br>[09:32] book. It was like the size of a<br>[09:33] pamphlet. Little tiny thing and it was<br>[09:35] called Tyranny of the Urgent. Uh I mean<br>[09:37] you could sit on the toilet and read it<br>[09:39] like you boom done. Um Tyranny of the<br>[09:41] Urgent. The messaging in that book was<br>[09:43] so strong. I was like, "This answers so<br>[09:46] many things I've dealt with<br>[09:47] professionally in my life." Like, you<br>[09:50] are so busy putting out fires and<br>[09:52] dealing with everyone else's emergencies<br>[09:54] that you never get to address what's<br>[09:56] important. And when you look at people<br>[09:57] that really build successful, you know,<br>[09:59] enterprises, these are people that have<br>[10:01] the ability to go that that's a<br>[10:04] distraction. You know, I got to focus on<br>[10:05] what's important. I know that you think<br>[10:07] that's important, but that's a<br>[10:08] distraction for the overall goal. And um<br>[10:11] that book Tyranny of the Urgent really<br>[10:13] helped me to kind of refocus that that's<br>[10:16] where the time blocking idea came from<br>[10:17] that you and I discussed weeks ago. It's<br>[10:19] like time blocking is for the important<br>[10:21] stuff and then the urgent stuff I kind<br>[10:24] of fill in where I can. Yeah. And it it<br>[10:26] takes real discipline to um to to slow<br>[10:29] down and re reposition, you know, to<br>[10:31] file that urgent thing wherever it<br>[10:33] belongs. Maybe it's not actually urgent.<br>[10:35] That takes a lot of like a lot of<br>[10:36] discipline like from whoever's whether<br>[10:38] you're project manager, business owner,<br>[10:40] whatever. There's another thing here<br>[10:42] that is related that this new meeting<br>[10:45] agenda did for me and it added<br>[10:47] transparent accountability. Uh first it<br>[10:49] clear calls out the issues transparently<br>[10:51] and we discuss them transparently. Then<br>[10:52] like there's a clear to-do list coming<br>[10:55] out of these. So okay, we address the<br>[10:56] issue it converts conversationally. What<br>[10:59] are the to-dos that came out of that<br>[11:01] discussion and who's going to own those<br>[11:02] to-dos? And the the thought is that like<br>[11:05] these are week max to-dos like so you're<br>[11:08] going to have them done by the next week<br>[11:09] or the next month whatever your cadence<br>[11:10] is for meetings.<br>[11:11] >> Yeah.<br>[11:11] >> Um and then you transparently you write<br>[11:13] those down and say by the next meeting<br>[11:14] you're going to do these things and<br>[11:16] every and everyone sees it everyone<br>[11:18] commits to the next meeting at the top<br>[11:19] of the meeting. We we don't start with<br>[11:21] that but it's in there as like a done or<br>[11:23] not done. If it's not done then it<br>[11:25] becomes an issue to converse about and<br>[11:26] so it adds this accountability layer<br>[11:28] that we were lacking in our at the<br>[11:31] mighty mo I would say like from a<br>[11:33] meeting to meeting you know people would<br>[11:34] promise things and sometimes they get<br>[11:36] lost sometimes not you know<br>[11:38] >> well I think one of the things that<br>[11:40] you're hitting on here is like the the<br>[11:42] difference between like two elements of<br>[11:44] a meeting some people treat meetings<br>[11:46] like they're an exchange of information<br>[11:48] right like we're just meeting and we're<br>[11:50] exchanging information so everybody<br>[11:51] knows what's going on and then there's<br>[11:53] the idea that we're having a meeting<br>[11:55] because action is tied to the meeting.<br>[11:58] And what you described is action is tied<br>[12:01] to the meeting. And that to me is is<br>[12:03] like the only reason to really have<br>[12:04] meetings. Um we're very proactive at<br>[12:07] Manana about disclosing um status of a<br>[12:10] project or things like that to clients.<br>[12:12] We're we're very um outgoing in that<br>[12:14] way. So we don't get a lot of like, hey,<br>[12:16] we should meet and have a you know<br>[12:17] discuss the status of my project. Um, so<br>[12:20] when I get like Zoom requests from<br>[12:22] clients, I'm very protective of my time<br>[12:25] because I'm like, hey, you know, we<br>[12:27] factored in like 10 or 12 or 15 meetings<br>[12:30] into your project. Like I factored that<br>[12:32] in when I bid the job and you want now<br>[12:33] you want to meet every Tuesday at 3.<br>[12:35] Okay, why do you want to meet every<br>[12:37] Tuesday at 3? Like you have access to<br>[12:39] you have access to the client portal.<br>[12:41] You you know what the milestones are.<br>[12:42] You know that we're ahead of schedule.<br>[12:44] You know that we're under budget. We<br>[12:46] have all of your assets. what do you<br>[12:47] want to meet every Tuesday at 3:00 for?<br>[12:49] And then you find out that it's just<br>[12:51] some kind of weird like emotional<br>[12:53] security blanket for them. Well, if<br>[12:55] you've got some weird emotional security<br>[12:57] blanket and and you're not happy with<br>[12:58] the tools we've already provided, we can<br>[13:01] do this, but it's going to be at an<br>[13:02] added cost.<br>[13:03] >> I wonder too like, you know, so you<br>[13:04] counted for 12 meetings. um if there was<br>[13:08] more formality about or more description<br>[13:10] because I'm sure they're formal but like<br>[13:11] it's like if we communicated why we<br>[13:14] chose 12 meetings and what's on the<br>[13:16] agenda for each meeting like if that<br>[13:18] would alleviate some of the anxiety that<br>[13:21] yeah like say we have a place for your<br>[13:23] concerns they're here they're on January<br>[13:26] 12th you know like or July 13th you know<br>[13:29] um we're thank you for sending that I've<br>[13:31] added it to the list you know that's<br>[13:32] what I wonder um well it's one way like<br>[13:35] a I think that this thing I'm doing now<br>[13:38] is going to be helpful for our team. Um,<br>[13:40] >> yeah.<br>[13:40] >> I also think like<br>[13:43] having this formal agenda and the way<br>[13:45] that we're going to be doing it, like I<br>[13:47] can't tell you how many times I've shown<br>[13:48] up to meetings and just been frustrated<br>[13:50] because there's no agenda and like it's<br>[13:52] not even clear to me why why we're<br>[13:54] there, what we're going to talk about<br>[13:55] almost every time, frankly, internally.<br>[13:58] Um and and I think this agenda, let's<br>[14:00] just say it'll help me, but also like it<br>[14:02] forces all the attend or the at least<br>[14:04] the leader of the meeting to show up<br>[14:06] prepared. I wish you the best of luck<br>[14:08] with this. The hard part is managing it<br>[14:09] and keeping it right because um just<br>[14:12] like everything else that we do, you<br>[14:14] assign it a process and then if you get<br>[14:17] weak or lax or um you know on the<br>[14:20] process and and it starts to lose its<br>[14:22] form, uh it can morph real quickly on<br>[14:25] you. So it just it takes discipline to<br>[14:27] maintain these things and your<br>[14:29] >> and the personalities of your people<br>[14:31] group kind of infect the way that the<br>[14:34] outcome happens.<br>[14:35] >> Yeah. And I think one cool thing I've<br>[14:37] been reading about, you know, we're<br>[14:39] considering going some hybrid EOS and<br>[14:42] hiring an imple.<br>[14:44] um part of the their bigger picture is<br>[14:47] like how do you know you have the right<br>[14:49] people at the company in and even if you<br>[14:52] have the right people are they in the<br>[14:53] right position and role at the company<br>[14:56] um and so like when I hear the language<br>[14:58] you use and I don't know if this right<br>[15:00] but like infected there are people at<br>[15:01] companies that poison the well for<br>[15:04] everybody and they can po they can do<br>[15:06] that quickly and I think like part of<br>[15:08] our job as like owners of agencies is to<br>[15:11] like figure out ways to find those<br>[15:13] people fret them and you know fire them<br>[15:16] you know you know get them out as soon<br>[15:17] as possible um if they exist and I I<br>[15:20] think like there's degrees of this too<br>[15:22] and this is what makes it hard that like<br>[15:24] for example a new employee takes a while<br>[15:26] to ramp up and you don't know if they're<br>[15:28] let's say they're slow to get to where<br>[15:30] they need to get you don't know if<br>[15:32] they're if they have the talent and<br>[15:33] ability for another three months<br>[15:36] >> I think the well poisoning is like that<br>[15:38] where you have to like really it's hard<br>[15:40] but you got to figure it out<br>[15:42] >> it comes with a certain<br>[15:44] comfort level, right? Um it falls into<br>[15:46] like those whole four stages of<br>[15:48] competency and things like that, right?<br>[15:49] But when they first start, they're<br>[15:51] they're still getting their feet on the<br>[15:52] ground. They're still getting a<br>[15:53] foundation, but once they feel like<br>[15:55] they've got a foundation, then they<br>[15:57] start growing opinions, right? And those<br>[15:59] opinions are like, "Toby's an idiot. He<br>[16:01] doesn't know what he's doing. These<br>[16:02] meetings suck." Right? And then all they<br>[16:04] do is repeat that to two or three<br>[16:06] people. Next thing you know, you got<br>[16:07] nine people that aren't happy. And<br>[16:09] you're going, "What happened a year ago?<br>[16:10] Everything was going great." you know,<br>[16:12] and it's and then you have to do some<br>[16:14] root cause analysis and then uh<br>[16:16] unfortunately liquidate somebody.<br>[16:18] >> And part of part part of this too is<br>[16:19] like the how you roll it out is<br>[16:21] important particularly with the bigger<br>[16:22] team probably. But like um<br>[16:26] one bad experience as you roll something<br>[16:29] out internally can ruin it forever. Like<br>[16:32] you know, let's say the fir you have a<br>[16:34] meeting and like you did it wrong or<br>[16:36] something and there's somebody in there<br>[16:38] says this sucked. I'm never doing this<br>[16:39] again. And yeah, then you run into this<br>[16:41] thing and you go, is it a poisoning of<br>[16:43] the well or is it just like this human<br>[16:45] tendency to be like, "That sucked. I'm<br>[16:47] never doing that again." You know,<br>[16:48] there's a<br>[16:49] >> there's a company I work with, by the<br>[16:51] way, along the poisoning. Um there's a<br>[16:53] guy who's been there forever. Every time<br>[16:55] I talk to him, he's like, "God, I hate<br>[16:57] working here. This sucks. Such and such<br>[16:59] of the company." And I don't even work<br>[17:00] there. He's telling me like all the<br>[17:01] things he hates about the company, you<br>[17:03] know? Um and he's been there forever.<br>[17:06] And like I I I don't know for sure, but<br>[17:08] like I can't I believe that he's<br>[17:10] probably like hurt the business<br>[17:12] significantly. Just this one guy and<br>[17:15] he's still there.<br>[17:15] >> I think back to my corporate experience<br>[17:17] and how many times did I share cubicle<br>[17:19] space with people that hated being there<br>[17:20] every day, you know, and it just drags<br>[17:23] you down. It affects your productivity.<br>[17:25] It affects the way you deal with<br>[17:26] clients, customers, co-workers,<br>[17:28] everything. The way you deal with<br>[17:29] vendors. Um, yeah. And it's amazing<br>[17:33] because there's that little switch in<br>[17:35] our own brains where we can change our<br>[17:36] perspective or our perception of<br>[17:38] something and we can see it from a<br>[17:39] completely different p. The facts don't<br>[17:41] change, but our reaction to those facts<br>[17:43] changes and then all of a sudden<br>[17:45] everything's better. And it's like it's<br>[17:47] so hard to pinpoint how the human brain<br>[17:51] can do that, right? But like you wish<br>[17:53] there was a magic switch you could hit<br>[17:54] externally for other people to go, man,<br>[17:56] stop being so negative, you know, see<br>[17:58] the positive here. like you got a job,<br>[18:00] you have a house, you drove a car to<br>[18:01] work today, like you're ahead of you're<br>[18:03] ahead of the rest of the planet. Um,<br>[18:05] people just struggle with trying to see<br>[18:08] the positive in things.<br>[18:09] >> Let's transition to another topic here<br>[18:11] that's uh not at all related. Um,<br>[18:14] >> if if you're tired of running a<br>[18:15] business, [laughter]<br>[18:18] >> hypothetically, [clears throat] we and<br>[18:20] you can listen to last week's episode<br>[18:22] that for the the conversation that<br>[18:23] spurred this, but the question from last<br>[18:25] week was basically like, uh, hey, I'm<br>[18:28] having [clears throat] a lot of trouble<br>[18:29] finding work. I'm a freelance<br>[18:31] uh, you know, I'm an unemployed<br>[18:33] freelance developer. That was kind of<br>[18:34] the question. How do I find work? Let's<br>[18:36] let's be generous and say that's what it<br>[18:38] was.<br>[18:39] >> Yes.<br>[18:41] >> Um, and then we got to talk after the<br>[18:42] show. So, I'm going to pitch this<br>[18:44] question. Um, pretend you were on<br>[18:46] Billiondollar WordPress Boss, which is a<br>[18:49] new show we're inventing for Discovery<br>[18:51] Network.<br>[18:52] >> It's Matt Matt Matt's going to produce<br>[18:55] it. It's going to be great. Um, and and<br>[18:58] it's called Billiondollar WordPress<br>[18:59] Boss.<br>[19:00] >> And the idea is like we set you in the<br>[19:03] middle of a city somewhere that where<br>[19:05] you know nobody and you have to use<br>[19:06] another name and you can't call on your<br>[19:08] former resources and all that. Um, and<br>[19:10] the question is like, uh, how do you get<br>[19:12] leads? How do you get sales? Where do<br>[19:14] you start, Kurt?<br>[19:15] >> I loved that. We This is so much fun for<br>[19:18] me cuz like just just the thinking of<br>[19:19] it, right? Like that whole billionaire<br>[19:21] boss show that I think Discovery did. I<br>[19:24] think Discovery um, with Grant Cardone<br>[19:26] and a bunch of people, they drop these<br>[19:27] people off in a city with nothing, like<br>[19:30] a piece of junk used car and a hundred<br>[19:32] bucks, right? And then you have to build<br>[19:34] a million-dollar business in 90 days or<br>[19:36] something. Um, so yeah, let's say you<br>[19:39] don't even have you don't even have<br>[19:41] access to the internet. You got a laptop<br>[19:42] in your backpack. You got let's say you<br>[19:44] got 200 bucks and you're starting from<br>[19:46] scratch. Dude, I it's such a fun<br>[19:49] challenge because you and I are so used<br>[19:51] to the agency world and dealing with all<br>[19:52] the bells and whistles of things. Like<br>[19:54] if you could start from scratch again,<br>[19:56] from a clean slate, like boom. Like I<br>[19:59] immediately I immediately would find the<br>[20:03] whatever the economic development office<br>[20:05] was for that area. In Hudchinson, they<br>[20:07] call it Startup Hutch. Um in<br>[20:10] Albuquerque, it was the South Valley<br>[20:12] Economic Development Center. But there's<br>[20:14] always some kind of like city or county<br>[20:18] subsidized organization that helps<br>[20:20] people launch new businesses. And those<br>[20:23] people always need startup websites. And<br>[20:26] so that gets your foot in the door. That<br>[20:28] helps you break the ice. Um people that<br>[20:31] uh that that old show American Pickers<br>[20:34] or whatever where they would go to<br>[20:35] people's junkyards and and and he would<br>[20:37] that one star would say, "Oh, you got to<br>[20:39] break the ice. Buy something small." And<br>[20:40] then you can work on getting better<br>[20:42] deals on bigger things. Right? It's like<br>[20:44] that I think in the web space. I'm going<br>[20:46] to get in with one of these<br>[20:47] organizations. I'm going to get a couple<br>[20:49] of startup packages going. I'm going to<br>[20:51] launch them quickly at super affordable<br>[20:53] rates. I'm going to break the ice and<br>[20:54] then I'm going to start asking who do<br>[20:56] you know that I should know so I can get<br>[20:58] better jobs.<br>[20:59] >> Yeah. I think one thing that you brought<br>[21:01] up that's kind of universal is like you<br>[21:03] got to build relationships first of all.<br>[21:05] And I think one thing to keep in mind is<br>[21:08] just show up to the thing. Choose the<br>[21:10] room you want to be in. Whether it's BNI<br>[21:12] or, you know, a local meetup or<br>[21:13] whatever. Uh could be the library you<br>[21:15] show up to every day, but like go<br>[21:17] somewhere where there are people with<br>[21:19] money to spend or or that have<br>[21:21] relationships. It could be the gym,<br>[21:22] frankly. Uh my dad once told me like he<br>[21:25] goes, "You should just join the priciest<br>[21:27] gym in Minneapolis and show up every<br>[21:29] day. That'd be your your your whole<br>[21:31] marketing plan." Like [laughter]<br>[21:33] I'm like there's a lot of logic to that.<br>[21:36] Um and so part of it just show up<br>[21:38] regularly. You got to keep showing up.<br>[21:40] People, you know, there's this human<br>[21:41] thing where you show up, people trust<br>[21:43] you. It doesn't matter if you're<br>[21:44] trustworthy or not. Like, oh, you've<br>[21:45] been here 10 times in a row. I trust<br>[21:47] you. Like, it's just a very human thing.<br>[21:49] Um, uh, get clear. So, you're there,<br>[21:52] you're talking to people. I think like<br>[21:54] get clear about what you do in specific<br>[21:57] so they can help you. You need to give<br>[21:59] them something to bite onto that they<br>[22:01] can maybe hire you or maybe introduce<br>[22:03] you. And also, the thing to be specific<br>[22:05] about might be, hey, I'm a freelancer<br>[22:08] who does WordPress work and I need help<br>[22:10] finding people who want to hire me. Like<br>[22:12] that could be the conversation. You<br>[22:13] don't have to like sugarcoat it all the<br>[22:15] time.<br>[22:15] >> You you're you're scratching the surface<br>[22:17] of one that that everyone says I'm<br>[22:20] crazy. Everyone says I'm wrong. Uh like<br>[22:22] for instance, I got the Hutchinson<br>[22:23] Kansas. I immediately looked up who else<br>[22:26] thinks there an agency in town. And and<br>[22:28] you would think Hutchinson small,<br>[22:29] there's no agencies. Well, do a Google<br>[22:30] search. All of a sudden there's<br>[22:31] agencies. Um I met these people in in<br>[22:34] one case. I went to their office and<br>[22:36] said, "Hey, I just want to introduce<br>[22:37] myself. You and I are in the same<br>[22:38] space." Um, because what you find out<br>[22:40] is, like you just said, get clear on<br>[22:43] what you offer. Get clear on what you<br>[22:45] do. I just got a referral two weeks ago<br>[22:48] from my competition in town because they<br>[22:51] messaged me on Facebook and said, "Hey,<br>[22:53] Kurt, I got this lady that wants this<br>[22:55] e-commerce website. It's more<br>[22:56] complicated than what we like to work<br>[22:57] on. Can we just refer her to you?" Yeah,<br>[23:00] I'll take it.<br>[23:00] >> Yeah. Also, like as you're looking at<br>[23:02] places, like I would look at where as I<br>[23:05] go to places. So you have to kind of go<br>[23:06] to understand it and maybe you can<br>[23:08] figure out some clues from people, but<br>[23:10] you want to go where the energy is. Like<br>[23:12] there are places that are boring and<br>[23:14] lame and nobody ever shares business.<br>[23:15] But if you go to a place that you know<br>[23:17] it almost right away, like you go in<br>[23:19] there, you start talking to people and<br>[23:21] stuff is happening and like somehow you<br>[23:23] got to figure out where those places<br>[23:25] are. The energy is good. Um I joined it.<br>[23:30] So, this sounds very self- serving and<br>[23:32] and<br>[23:33] >> yeah,<br>[23:34] >> so I'm thinking about how I would do it.<br>[23:36] Like Kansas has, you know, counties and<br>[23:38] cities like everywhere else, but each of<br>[23:40] these cities and counties has programs,<br>[23:44] leadership programs or business<br>[23:45] development programs or things like<br>[23:47] that. And I found that, you know, a you<br>[23:49] could sign up and be a free student,<br>[23:51] right? Because they're subsidized. So,<br>[23:52] you could take the course and become a<br>[23:54] free student. What What are you going to<br>[23:56] do? Well, you're going to be in a room<br>[23:57] with 11 other people that are launching<br>[23:59] a business and you know how to make<br>[24:01] websites for startups. Like, so that's<br>[24:03] one right there. And you're going to get<br>[24:04] to know those people because you're<br>[24:05] going to be in class with them, you<br>[24:06] know, once a week for 12 weeks or<br>[24:08] something silly, right? So, so there's<br>[24:10] that. Um, there's a leadership cohort in<br>[24:12] the county that I'm in. And so, uh,<br>[24:15] bunch of people get together and meet<br>[24:16] and they're from all over the place, the<br>[24:19] different levels of executive leadership<br>[24:21] to, you know, aators there. Um, I just I<br>[24:25] I think about it's such a cool idea,<br>[24:27] right? Go to a city. You don't know<br>[24:29] anybody. You can't use your real name.<br>[24:30] You can't use your contact list. You got<br>[24:32] 200 bucks. What do you do? Right? Well,<br>[24:34] you go to where the internet is. Go to<br>[24:36] the coffee shop. Go to the library. Go<br>[24:38] to those places, connect to the web, and<br>[24:40] and start doing stuff. Um, get active on<br>[24:44] social. make sure that you, you know,<br>[24:46] use some like local SEO talent, you<br>[24:48] know, to kind of drive things to what<br>[24:49] you're working on and that you're new in<br>[24:50] town and that you're uh feverishly<br>[24:53] actively uh looking for work. Um I'm not<br>[24:56] saying beg for work. I'm just saying<br>[24:57] make sure people know you're available.<br>[24:59] >> Yeah. And I think anytime you go<br>[25:01] somewhere these days, you usually know<br>[25:02] who else is going to be there. Like<br>[25:04] there's usually an attendee list. Like<br>[25:05] if you do meetup.com or something like<br>[25:07] that, you can usually get a good sense<br>[25:08] of who's going to be there. do your<br>[25:10] research on them, you know, like figure<br>[25:12] out who they are on LinkedIn and you<br>[25:14] know, it's not easy. It takes some time,<br>[25:16] but like, and I'm not saying get creepy,<br>[25:18] but like come prepared to talk with<br>[25:20] topics that might be of interest to<br>[25:22] them. Like you're going to an event with<br>[25:23] a lot of startup people, maybe look up<br>[25:25] some recent startupy articles on some<br>[25:28] startup website that, you know, some<br>[25:30] news site. Um, similarly, you're at the<br>[25:33] meeting and if somebody's um looking to<br>[25:36] be connected in a similar way, connect<br>[25:38] them with someone else at the meeting.<br>[25:40] This costs nothing. I just talked to<br>[25:42] him. Hey, you should meet each other.<br>[25:43] Like, be a good host even though you're<br>[25:45] a guest there. You know, you can you can<br>[25:47] you can make a lot of friends just by<br>[25:50] helping people.<br>[25:51] >> I think it's fun to um make a customer<br>[25:55] by being a customer. Like go in and and<br>[25:58] you know, you got those $200 to spend,<br>[26:00] right? So, you go in and you buy the<br>[26:02] coffee. Uh, I'm in the bicycling. You<br>[26:04] know, maybe I'm going to go and buy a<br>[26:05] bicycle tube at the bike shop. But<br>[26:07] that's going to create um a I'm doing<br>[26:09] business with them. I'm breaking that<br>[26:11] ice. I'm going to create a relationship.<br>[26:12] I'm going to have a conversation. I'm<br>[26:14] not just going to buy the tube. Right?<br>[26:15] I'm going to be like, "Hey, it's a<br>[26:16] really nice store. How long has it been<br>[26:18] here? You know, how many bikes do you<br>[26:19] guys sell every month? Oh, this is so<br>[26:20] cool. I didn't even know that this was<br>[26:21] here." Right? You're having this<br>[26:23] conversation. That conversation is going<br>[26:25] to build um equity in your relationship.<br>[26:28] And so they might not need a new<br>[26:29] website, but you know what? They do<br>[26:31] business with 25 other people in town<br>[26:34] and somebody's going to want something<br>[26:36] done and hopefully you're the name at<br>[26:37] the tip of their tongue.<br>[26:38] >> Yeah. I also think like co-working<br>[26:40] spaces, like throw that that on the list<br>[26:42] of places you might go. Um, specifically<br>[26:45] talk to the front desk people at<br>[26:47] co-working spaces. They know everybody<br>[26:49] there. They they're connectors usually.<br>[26:51] Um, maybe ask them for a job, like, you<br>[26:54] know, tell them what's up. Tell them you<br>[26:56] need work. And um a lot I think if you<br>[26:59] find the right place and right people<br>[27:00] like people want to help I think but you<br>[27:03] got to ask and you got to be specific.<br>[27:04] >> You you got to get involved right? So I<br>[27:08] think that that is you know and that's<br>[27:09] something that AI can't do for you. AI<br>[27:11] can't replace you. People want the<br>[27:13] relationship. They want that you know<br>[27:15] human in the loop experience. And so you<br>[27:18] know I I really drive back and I look at<br>[27:21] like where did the success of Mรฑana Nas<br>[27:23] really come from? It didn't come from<br>[27:25] Facebook ads. It didn't come from fancy<br>[27:27] tricks and stuff. It came from uh<br>[27:29] networking, shaking hands, going to<br>[27:31] meetings, getting on podcasts. Um, you<br>[27:34] know, again, I'veorked with a lot of<br>[27:36] people that would say that, you know,<br>[27:38] that's my competition, but I usually get<br>[27:40] work from the relationships that should<br>[27:42] be with my competition because we have<br>[27:44] niches. We we have niches that are<br>[27:46] different than each other. So, we're<br>[27:47] able to share and refer work back and<br>[27:49] forth.<br>[27:50] >> Yeah. I I my experience has been like<br>[27:52] that it's almost like less of a you<br>[27:57] don't it's not complex like getting work<br>[28:00] is about human relationships and we're<br>[28:02] all have a certain level of talent and<br>[28:04] ability at human relationships and I<br>[28:06] think like the more you lean into that<br>[28:08] and this is where last week we got uh we<br>[28:11] were yelling about marketing verse sales<br>[28:13] like I mean the one thing we're hitting<br>[28:15] on 100% here is we are in a sales<br>[28:18] mentality when with all this We're<br>[28:20] saying how do we sell? We're not saying<br>[28:21] how do we get our brand out there? How<br>[28:23] do we market? Like the sales mentality,<br>[28:26] I think, is everything. And it's<br>[28:28] probably where businesses fail and<br>[28:30] succeed just generally speaking. Like if<br>[28:32] you take the organization as a whole,<br>[28:34] how big of a sales mentality do they<br>[28:36] have? You know, it's probably it'd be an<br>[28:38] interesting study like to see like let's<br>[28:41] take every 20 person organization in the<br>[28:43] country and rate them on a sales how big<br>[28:46] a sales uh personality do they have? And<br>[28:48] I'm not talking about what they do. Like<br>[28:50] they could they could be a a fix it shop<br>[28:53] for your local automobile, you know,<br>[28:54] like but how big of are they do they<br>[28:56] because sales people have an urgency<br>[28:58] about them that is it's a magnet.<br>[29:01] >> Yeah. I think you hit something very um<br>[29:05] important and I don't want to glaze over<br>[29:07] it. Sales is like that's the first<br>[29:09] thing. A lot of people say, "Oh, I'm<br>[29:11] going to build a website and I'm going<br>[29:12] to this and I'm going to market that and<br>[29:13] I'm going to do the other thing." And<br>[29:14] and we get all excited about all these<br>[29:16] distractions, but distractions don't put<br>[29:17] a dime in your bank account. To me, like<br>[29:20] again, if I'm dropped off in a city with<br>[29:22] $200 in my pocket and a laptop, right?<br>[29:25] My number one goal is how many people<br>[29:27] can I meet? How quickly can I meet them?<br>[29:29] How many conversations can I have? And<br>[29:31] which of those conversations is going to<br>[29:33] lead to conversion? Each of those<br>[29:34] conversations, I'm going to be<br>[29:36] identifying a need and supplying a<br>[29:38] solution. And if someone says, "Hey,<br>[29:40] that sounds like something I need." Or,<br>[29:41] "Hey, you need to talk to my nephew."<br>[29:43] Or, "You need to whatever." I'm going to<br>[29:44] follow that up. Like the number one<br>[29:45] thing is sales and revenue. See, I'm<br>[29:47] getting excited. I can hear it in my own<br>[29:49] voice. So, the number one thing is<br>[29:50] revenue. As soon as I get that little<br>[29:52] bit of revenue, Toby, well, well, now I<br>[29:54] can go, "Okay, I've got revenue. Now, I<br>[29:56] can think about how would I market this<br>[29:59] and scale it and increase it and<br>[30:01] continue my sales."<br>[30:02] >> Yeah, maybe. I I don't even go there. I<br>[30:04] just go, "Let's go get<br>[30:05] >> I just keep selling." [laughter]<br>[30:07] the one thing you brought up that's<br>[30:08] really uh as we're as I'm thinking back<br>[30:12] through this conversation today about<br>[30:13] the uh billion-dollar WordPress<br>[30:16] billionaire whatever um we haven't<br>[30:18] talked about marketing at all like that<br>[30:20] what didn't even occur to us as a thing<br>[30:22] to do<br>[30:23] >> no which<br>[30:24] >> uh instead we<br>[30:27] didn't mention websites we didn't<br>[30:28] mention like colors or logo and because<br>[30:31] when I think about this you've dropped<br>[30:33] somewhere you need work and this is this<br>[30:35] person who maybe it's you listening and<br>[30:37] you're like, "Ah, I can't find work."<br>[30:39] Um, this is how I approach. I go, I find<br>[30:42] I would find the people and I hear<br>[30:44] someone say, "Hey, I really need a<br>[30:47] WordPress uh Woo Commerce site. Do you<br>[30:50] do that?" I would, you know, because I<br>[30:51] have that skill set, I say, "Yes, I do."<br>[30:54] "Do you have a website?" "Yes, I do, but<br>[30:56] um let me email it to you later."<br>[30:59] >> [laughter]<br>[30:59] >> And now that I have their info, I have<br>[31:01] their contact info, I have what they<br>[31:03] need, I run home, I build a WooCommerce<br>[31:06] marketing site. I say, "Here's my<br>[31:07] website, um, and it's exactly what they<br>[31:10] need. It looks professional, you know,<br>[31:12] like I I wouldn't overthink the<br>[31:13] marketing piece until I have someone to<br>[31:15] sell to." Yeah, I'm um 100% I don't know<br>[31:18] why I'm so focused on revenue lately<br>[31:20] because things have grown pretty decent,<br>[31:21] but um my last few lives and shows have<br>[31:25] really been based on like revenue. like<br>[31:27] we've got to get back to being focused<br>[31:29] on sales and revenue and all of this all<br>[31:32] of this other stuff like I'm hearing I'm<br>[31:36] seeing a ton from people in our space<br>[31:38] Toby with I'm going to vibe code this<br>[31:40] and I'm making these tools and these<br>[31:41] plugins and this and I'm experimenting<br>[31:43] with this page builder and I'm doing and<br>[31:44] it's like okay that's great that you<br>[31:46] want to be at the threshold of<br>[31:48] advancement in our space like that's<br>[31:50] great if you want to be at the top of<br>[31:51] everything that's wonderful but I don't<br>[31:54] think the message today is driven to<br>[31:55] those people. I think the message today<br>[31:58] is like don't waste time getting<br>[32:00] distracted by all these superfluous<br>[32:01] activities. WordPress by itself out of<br>[32:04] the box with like five or six key<br>[32:06] plugins. You can run an entirely<br>[32:09] profitable agency off of that and just<br>[32:11] get going. Just just create revenue,<br>[32:13] build projects, and get going. And you<br>[32:15] can always get to this other stuff when<br>[32:17] time comes.<br>[32:18] >> Thank you. That's a great way to segue<br>[32:20] to the ending of our show here. Uh Kurt,<br>[32:23] how can people get in touch with you?<br>[32:24] Well, you can reach me at LinkedIn. I'm<br>[32:26] the only Kurt Vonan on LinkedIn. I<br>[32:28] encourage you to connect. Uh for<br>[32:30] business, uh we are mรฑana noms and mรฑana<br>[32:33] noms is the call sign for all of our<br>[32:35] socials and our.com. Toby, you<br>[32:37] >> I am on LinkedIn Toby and the last name<br>[32:39] is C R Y NS. You can find me at<br>[32:41] themo.com. That's tmi gtm.com<br>[32:47] where we do WordPress stuff and SEO<br>[32:50] stuff. So, um thanks everyone for<br>[32:52] joining us today. always like to have<br>[32:54] you. Please like, send us emails,<br>[32:56] comments on any wherever you're watching<br>[32:58] or listening. Send us a comment if you<br>[32:59] have a question or an idea for a new<br>[33:01] show. Uh look forward to seeing you next<br>[33:02] week.<br>[33:03] >> Awesome. This is a fun one.
Well, here we are again, folks. Welcome to another agency action show. I'm here with Toby Kines. My name is Kurt. Toby, talk to me about uh meetings and how much you love having meetings. I've realized um I really don't like having meetings and going to meetings and holding them. But then it got me thinking like what would a good meeting look like? And there's a whole like
there are business consultancies and whole like a whole vertical of business consultancies that are focused almost exclusively on this topic. Um, and I was looking into one that's called EOS and um, there are others and I'm sure they're all fine in their own ways, but specifically I was looking at it from a meeting management standpoint and like what is a great meeting? How do you have
a meeting where people leave the meeting and go, "Thank you. I'm glad we had that meeting." Even if you know in the book and the the philosophy of EOS that they're like, you want people to say it's a great meeting, but I'm not aiming for great. I'm aiming like great in the context of business meetings because nobody really wants to be in them. >> Um but and so then I got into it and I
actually so EOS has a its own meeting agenda template and philosophy and I actually implemented I'm imple implementing this agenda at the mighty mo for any recurring meeting. So this is like weekly meetings between me and my operations team between me and my SEO team between operations team and project management team like we're implementing that we're rolling it out. We had our
first two today and I got to say it's I felt way better about the meeting the meeting these two meetings today than I have about any previous one. And I think part of the philosophy behind the EOS thing is that uh every meeting has its same time every week. It's they recommend 90 minutes but um you know you can decide that I guess but uh same agenda every meeting and it always ends
on time. And this is like a problem. This is part of why I hate meetings is because they're always going over and I'm always like, "Ah, really?" Like again, now I'm late for the next meeting. And so I did two today. And even though we didn't even plan enough time because like I was like, "I want to share this meeting template idea with you." Um the so the meetings were
actually like in in context of that way shorter than they would have otherwise been and we still I felt like got through way more than we otherwise would have historically. So, wanted to ask you, Kurt, what are some reasons meetings suck in your experience? >> I think in general, when you say agenda, that that to me is like that's the lynch pin. That's that's
the thing. Um, I've worked with a ton, you know, I have that corporate experience and I've worked for a lot of car dealerships and a lot of car dealerships aren't run by people that are leadership experts. They're run by people that are car enthusiasts. And so I know what bad meetings look like. Uh I've also had the privilege of I know this this everyone's going to think this
guy owes me money. Chris Badget at Lifter LMS, I go to his meetings. He's like a master at running a good meeting. Um it's interactive. You know, what are our wins? What are our losses? What what are our key points? What are our focus points? And you know, what do we pin to talk about later? You know, one-on-one or something like that. I think one of
the things that I hate about meetings is when you're in a room with 10 people and it seems like the meeting is for two people and a dude, you know, and you're sitting there like an idiot. Like I don't even know why I'm here. Like that for me is like these are not meetings I need to be in. >> Yeah. I think even with the EOS template, it doesn't solve that specific
problem. Um what it does solve, however, is is let's work on the most important stuff. let's first define how do we define importance. So there's a lot of like pre-work you do um just to define from from the business standpoint what's important and then when you get to these meetings you go like okay we now have the context for how do we define important which are these items and then
you rank them by the order of importance to the business and um and and the idea is like you're not spending a lot of time like talking about what you're doing but like solving the issues but I could still see a scenario where two people are going back and forth on a specific issue for a long period of time. It could be the whole meeting frankly because the way that EOS sets it
up is like you have your most important thing first and you don't stop until either that issues done or the time for the meeting's done and and so you could potentially have two people talking the whole meeting and I yeah I don't know how you solved that. >> So so in those instances um and and I'll drive this back to my work at Suzuki, right? I was in charge of a group of six
people that did all the publications and training for Suzuki. If I was concerned, if my number one priority was an e-learning module uh being done by Michelle, uh me and Michelle would book a room and have a meeting, right? Like like that would be the meeting and here's my agenda for the meeting with Michelle. I wouldn't bring, you know, Bill, Tristan, and Ron into the meeting
with Michelle to talk about the e-learning module, right? Um if there was a uh something that had to be edited for a service manual, uh I would meet with Ron one-on-one, but I wouldn't bring in again the whole team, right? for those and that's why the agenda thing is so important because if I'm going to have a group meeting right what are the what are the top most important
things that affect the group and then boom boom boom so I think when we have a team meeting and again I'm going to drive back to the lifter LMS example when we have a team meeting it's really to educate the team as to what all of the stakeholders are actively doing or or the process or the progress of things and so we'll take a look at like you know the the flowchart for sprints or
the Gant chart or whatever you want to call it, right? So, development's working on this, sales is working on this, da da da da da, customer service is knocking it out of the park with these five things. Here's three new testimonials, sales is good, here's the the, you know, the bundles we sold this week. And then all of the details get handled in individual meetings for
development with those individual stakeholders. I think I'm just guessing here maybe and from experience like that I've seen at the Mighty M where that model potentially has a shortcoming that would need to be addressed is often times the issues surface in these conversations with the team that the issues even though they're really important wouldn't otherwise surface.
I'll give you an example. Um, recently I've been having these like one-off conversations with people on my team, like about a specific pro project and asking questions about how it's going. And I'm getting different answers from different people. Oh, it's going great. Going great. The next guy is like, no, it's going off the rails. And I'm like, um, I think if we had had a team meeting
that would have surfaced and like, hey, how's it going? Going great. Sucks. Like it' be like going off the rails. Like like maybe >> I don't know. Yeah, I had to do a lot of leg work to get there. Yeah, I I do see your point. If we again using Lifter as the example because that's, you know, my my most recent experience. Um, Lifter just came out with the events add-on,
right? So, you can do live Zoom events or inerson events attached to your website. And during one of those team meetings, Chris unveiled to the rest of us underlings that, you know, the this events add-on was going to come out. Now I work on the customer service team and so I'm responsible to like show it to people, you know, teach people how to use it and all that kind of stuff, but
it was still in development. And Brian, the developer, was like, "Yeah, the events thing's kind of cool. It's going to XYZ." And I was like, "Whoa, whoa, whoa, hold on." Like the feedback we've gotten from stakeholders already is that we wanted to do X, Y, and Z in addition to what you just said. And then he goes, "Oh, that's a good idea." Right? But
then we took that discussion to Slack for some details between him and I. And when they released the events package, it did exactly what I wanted it to do and Brian knocked it out of the park. So to your point, there there are things that come up, you know, through the agenda and through sharing things with the team. There are things there there's elements that come up, but we don't
absorb the meeting with those things. We give the opportunity for fine-tuning outside that meeting. >> Yeah. I I also think one thing I noticed today in my two meetings that use the new EOS format. I noticed because I was in charge of leading the meetings and we have a firm schedule uh firm agenda and we have places to put things that like and this is just me and one other person
in both meetings and I noticed they were either them or I were bringing up things that were tangential to what we were currently dealing with. Like we're talking about an issue and they say, "Well, what about this?" And it's like I can see how it relates. And it was really nice to be able to say like, "Thank you for sharing that. I'm going to put that at the bottom of the issues
list and if we have time later today, we'll get to it. Otherwise, we'll deal with it a different way." >> It's like our show notes. [laughter] >> Yeah, it is. Yeah. >> Well, we'll drive these uh these crappy notes down to the bottom and if we run out of time, we'll talk about it. >> And I think the reality is is that like those tangential things probably weren't
as important like first of all uh and probably they're, you know, they don't deserve to be injected at the top. And we notice this all the time like in our company that like perceived emergencies push everything down but there's no like we don't currently have like a great triage system to say like slow down let's think about where this emergency fits amongst our other priorities. And I
think like this meeting agenda handles that for meetings. It doesn't handle it for our business necessarily but like that happens at meetings all the time where someone brings something up and in my view derails the whole conversation of whatever was being brought up or conversed about. That's so important from a business perspective. Um I was doing some um study I I I don't want to
get why right but but one of the required readings for this study that I was in and I'm going back like I think it was 2007 or 8 um was a little tiny book. It was like the size of a pamphlet. Little tiny thing and it was called Tyranny of the Urgent. Uh I mean you could sit on the toilet and read it like you boom done. Um Tyranny of the Urgent. The messaging in that book was
so strong. I was like, "This answers so many things I've dealt with professionally in my life." Like, you are so busy putting out fires and dealing with everyone else's emergencies that you never get to address what's important. And when you look at people that really build successful, you know, enterprises, these are people that have the ability to go that that's a
distraction. You know, I got to focus on what's important. I know that you think that's important, but that's a distraction for the overall goal. And um that book Tyranny of the Urgent really helped me to kind of refocus that that's where the time blocking idea came from that you and I discussed weeks ago. It's like time blocking is for the important
stuff and then the urgent stuff I kind of fill in where I can. Yeah. And it it takes real discipline to um to to slow down and re reposition, you know, to file that urgent thing wherever it belongs. Maybe it's not actually urgent. That takes a lot of like a lot of discipline like from whoever's whether you're project manager, business owner, whatever. There's another thing here
that is related that this new meeting agenda did for me and it added transparent accountability. Uh first it clear calls out the issues transparently and we discuss them transparently. Then like there's a clear to-do list coming out of these. So okay, we address the issue it converts conversationally. What are the to-dos that came out of that discussion and who's going to own those
to-dos? And the the thought is that like these are week max to-dos like so you're going to have them done by the next week or the next month whatever your cadence is for meetings. >> Yeah. >> Um and then you transparently you write those down and say by the next meeting you're going to do these things and every and everyone sees it everyone commits to the next meeting at the top
of the meeting. We we don't start with that but it's in there as like a done or not done. If it's not done then it becomes an issue to converse about and so it adds this accountability layer that we were lacking in our at the mighty mo I would say like from a meeting to meeting you know people would promise things and sometimes they get lost sometimes not you know
>> well I think one of the things that you're hitting on here is like the the difference between like two elements of a meeting some people treat meetings like they're an exchange of information right like we're just meeting and we're exchanging information so everybody knows what's going on and then there's the idea that we're having a meeting because action is tied to the meeting.
And what you described is action is tied to the meeting. And that to me is is like the only reason to really have meetings. Um we're very proactive at Manana about disclosing um status of a project or things like that to clients. We're we're very um outgoing in that way. So we don't get a lot of like, hey, we should meet and have a you know discuss the status of my project. Um, so
when I get like Zoom requests from clients, I'm very protective of my time because I'm like, hey, you know, we factored in like 10 or 12 or 15 meetings into your project. Like I factored that in when I bid the job and you want now you want to meet every Tuesday at 3. Okay, why do you want to meet every Tuesday at 3? Like you have access to you have access to the client portal.
You you know what the milestones are. You know that we're ahead of schedule. You know that we're under budget. We have all of your assets. what do you want to meet every Tuesday at 3:00 for? And then you find out that it's just some kind of weird like emotional security blanket for them. Well, if you've got some weird emotional security blanket and and you're not happy with
the tools we've already provided, we can do this, but it's going to be at an added cost. >> I wonder too like, you know, so you counted for 12 meetings. um if there was more formality about or more description because I'm sure they're formal but like it's like if we communicated why we chose 12 meetings and what's on the agenda for each meeting like if that
would alleviate some of the anxiety that yeah like say we have a place for your concerns they're here they're on January 12th you know like or July 13th you know um we're thank you for sending that I've added it to the list you know that's what I wonder um well it's one way like a I think that this thing I'm doing now is going to be helpful for our team. Um,
>> yeah. >> I also think like having this formal agenda and the way that we're going to be doing it, like I can't tell you how many times I've shown up to meetings and just been frustrated because there's no agenda and like it's not even clear to me why why we're there, what we're going to talk about almost every time, frankly, internally. Um and and I think this agenda, let's
just say it'll help me, but also like it forces all the attend or the at least the leader of the meeting to show up prepared. I wish you the best of luck with this. The hard part is managing it and keeping it right because um just like everything else that we do, you assign it a process and then if you get weak or lax or um you know on the process and and it starts to lose its
form, uh it can morph real quickly on you. So it just it takes discipline to maintain these things and your >> and the personalities of your people group kind of infect the way that the outcome happens. >> Yeah. And I think one cool thing I've been reading about, you know, we're considering going some hybrid EOS and hiring an imple. um part of the their bigger picture is
like how do you know you have the right people at the company in and even if you have the right people are they in the right position and role at the company um and so like when I hear the language you use and I don't know if this right but like infected there are people at companies that poison the well for everybody and they can po they can do that quickly and I think like part of
our job as like owners of agencies is to like figure out ways to find those people fret them and you know fire them you know you know get them out as soon as possible um if they exist and I I think like there's degrees of this too and this is what makes it hard that like for example a new employee takes a while to ramp up and you don't know if they're
let's say they're slow to get to where they need to get you don't know if they're if they have the talent and ability for another three months >> I think the well poisoning is like that where you have to like really it's hard but you got to figure it out >> it comes with a certain comfort level, right? Um it falls into like those whole four stages of
competency and things like that, right? But when they first start, they're they're still getting their feet on the ground. They're still getting a foundation, but once they feel like they've got a foundation, then they start growing opinions, right? And those opinions are like, "Toby's an idiot. He doesn't know what he's doing. These meetings suck." Right? And then all they
do is repeat that to two or three people. Next thing you know, you got nine people that aren't happy. And you're going, "What happened a year ago? Everything was going great." you know, and it's and then you have to do some root cause analysis and then uh unfortunately liquidate somebody. >> And part of part part of this too is like the how you roll it out is
important particularly with the bigger team probably. But like um one bad experience as you roll something out internally can ruin it forever. Like you know, let's say the fir you have a meeting and like you did it wrong or something and there's somebody in there says this sucked. I'm never doing this again. And yeah, then you run into this thing and you go, is it a poisoning of
the well or is it just like this human tendency to be like, "That sucked. I'm never doing that again." You know, there's a >> there's a company I work with, by the way, along the poisoning. Um there's a guy who's been there forever. Every time I talk to him, he's like, "God, I hate working here. This sucks. Such and such of the company." And I don't even work
there. He's telling me like all the things he hates about the company, you know? Um and he's been there forever. And like I I I don't know for sure, but like I can't I believe that he's probably like hurt the business significantly. Just this one guy and he's still there. >> I think back to my corporate experience and how many times did I share cubicle
space with people that hated being there every day, you know, and it just drags you down. It affects your productivity. It affects the way you deal with clients, customers, co-workers, everything. The way you deal with vendors. Um, yeah. And it's amazing because there's that little switch in our own brains where we can change our perspective or our perception of
something and we can see it from a completely different p. The facts don't change, but our reaction to those facts changes and then all of a sudden everything's better. And it's like it's so hard to pinpoint how the human brain can do that, right? But like you wish there was a magic switch you could hit externally for other people to go, man, stop being so negative, you know, see
the positive here. like you got a job, you have a house, you drove a car to work today, like you're ahead of you're ahead of the rest of the planet. Um, people just struggle with trying to see the positive in things. >> Let's transition to another topic here that's uh not at all related. Um, >> if if you're tired of running a business, [laughter] >> hypothetically, [clears throat] we and
you can listen to last week's episode that for the the conversation that spurred this, but the question from last week was basically like, uh, hey, I'm having [clears throat] a lot of trouble finding work. I'm a freelance uh, you know, I'm an unemployed freelance developer. That was kind of the question. How do I find work? Let's let's be generous and say that's what it
was. >> Yes. >> Um, and then we got to talk after the show. So, I'm going to pitch this question. Um, pretend you were on Billiondollar WordPress Boss, which is a new show we're inventing for Discovery Network. >> It's Matt Matt Matt's going to produce it. It's going to be great. Um, and and it's called Billiondollar WordPress Boss. >> And the idea is like we set you in the
middle of a city somewhere that where you know nobody and you have to use another name and you can't call on your former resources and all that. Um, and the question is like, uh, how do you get leads? How do you get sales? Where do you start, Kurt? >> I loved that. We This is so much fun for me cuz like just just the thinking of it, right? Like that whole billionaire
boss show that I think Discovery did. I think Discovery um, with Grant Cardone and a bunch of people, they drop these people off in a city with nothing, like a piece of junk used car and a hundred bucks, right? And then you have to build a million-dollar business in 90 days or something. Um, so yeah, let's say you don't even have you don't even have
access to the internet. You got a laptop in your backpack. You got let's say you got 200 bucks and you're starting from scratch. Dude, I it's such a fun challenge because you and I are so used to the agency world and dealing with all the bells and whistles of things. Like if you could start from scratch again, from a clean slate, like boom. Like I immediately I immediately would find the
whatever the economic development office was for that area. In Hudchinson, they call it Startup Hutch. Um in Albuquerque, it was the South Valley Economic Development Center. But there's always some kind of like city or county subsidized organization that helps people launch new businesses. And those people always need startup websites. And so that gets your foot in the door. That
helps you break the ice. Um people that uh that that old show American Pickers or whatever where they would go to people's junkyards and and and he would that one star would say, "Oh, you got to break the ice. Buy something small." And then you can work on getting better deals on bigger things. Right? It's like that I think in the web space. I'm going
to get in with one of these organizations. I'm going to get a couple of startup packages going. I'm going to launch them quickly at super affordable rates. I'm going to break the ice and then I'm going to start asking who do you know that I should know so I can get better jobs. >> Yeah. I think one thing that you brought up that's kind of universal is like you
got to build relationships first of all. And I think one thing to keep in mind is just show up to the thing. Choose the room you want to be in. Whether it's BNI or, you know, a local meetup or whatever. Uh could be the library you show up to every day, but like go somewhere where there are people with money to spend or or that have relationships. It could be the gym,
frankly. Uh my dad once told me like he goes, "You should just join the priciest gym in Minneapolis and show up every day. That'd be your your your whole marketing plan." Like [laughter] I'm like there's a lot of logic to that. Um and so part of it just show up regularly. You got to keep showing up. People, you know, there's this human thing where you show up, people trust
you. It doesn't matter if you're trustworthy or not. Like, oh, you've been here 10 times in a row. I trust you. Like, it's just a very human thing. Um, uh, get clear. So, you're there, you're talking to people. I think like get clear about what you do in specific so they can help you. You need to give them something to bite onto that they can maybe hire you or maybe introduce
you. And also, the thing to be specific about might be, hey, I'm a freelancer who does WordPress work and I need help finding people who want to hire me. Like that could be the conversation. You don't have to like sugarcoat it all the time. >> You you're you're scratching the surface of one that that everyone says I'm crazy. Everyone says I'm wrong. Uh like
for instance, I got the Hutchinson Kansas. I immediately looked up who else thinks there an agency in town. And and you would think Hutchinson small, there's no agencies. Well, do a Google search. All of a sudden there's agencies. Um I met these people in in one case. I went to their office and said, "Hey, I just want to introduce myself. You and I are in the same
space." Um, because what you find out is, like you just said, get clear on what you offer. Get clear on what you do. I just got a referral two weeks ago from my competition in town because they messaged me on Facebook and said, "Hey, Kurt, I got this lady that wants this e-commerce website. It's more complicated than what we like to work on. Can we just refer her to you?" Yeah,
I'll take it. >> Yeah. Also, like as you're looking at places, like I would look at where as I go to places. So you have to kind of go to understand it and maybe you can figure out some clues from people, but you want to go where the energy is. Like there are places that are boring and lame and nobody ever shares business. But if you go to a place that you know
it almost right away, like you go in there, you start talking to people and stuff is happening and like somehow you got to figure out where those places are. The energy is good. Um I joined it. So, this sounds very self- serving and and >> yeah, >> so I'm thinking about how I would do it. Like Kansas has, you know, counties and cities like everywhere else, but each of
these cities and counties has programs, leadership programs or business development programs or things like that. And I found that, you know, a you could sign up and be a free student, right? Because they're subsidized. So, you could take the course and become a free student. What What are you going to do? Well, you're going to be in a room with 11 other people that are launching
a business and you know how to make websites for startups. Like, so that's one right there. And you're going to get to know those people because you're going to be in class with them, you know, once a week for 12 weeks or something silly, right? So, so there's that. Um, there's a leadership cohort in the county that I'm in. And so, uh, bunch of people get together and meet
and they're from all over the place, the different levels of executive leadership to, you know, aators there. Um, I just I I think about it's such a cool idea, right? Go to a city. You don't know anybody. You can't use your real name. You can't use your contact list. You got 200 bucks. What do you do? Right? Well, you go to where the internet is. Go to
the coffee shop. Go to the library. Go to those places, connect to the web, and and start doing stuff. Um, get active on social. make sure that you, you know, use some like local SEO talent, you know, to kind of drive things to what you're working on and that you're new in town and that you're uh feverishly actively uh looking for work. Um I'm not saying beg for work. I'm just saying
make sure people know you're available. >> Yeah. And I think anytime you go somewhere these days, you usually know who else is going to be there. Like there's usually an attendee list. Like if you do meetup.com or something like that, you can usually get a good sense of who's going to be there. do your research on them, you know, like figure out who they are on LinkedIn and you
know, it's not easy. It takes some time, but like, and I'm not saying get creepy, but like come prepared to talk with topics that might be of interest to them. Like you're going to an event with a lot of startup people, maybe look up some recent startupy articles on some startup website that, you know, some news site. Um, similarly, you're at the meeting and if somebody's um looking to
be connected in a similar way, connect them with someone else at the meeting. This costs nothing. I just talked to him. Hey, you should meet each other. Like, be a good host even though you're a guest there. You know, you can you can you can make a lot of friends just by helping people. >> I think it's fun to um make a customer by being a customer. Like go in and and
you know, you got those $200 to spend, right? So, you go in and you buy the coffee. Uh, I'm in the bicycling. You know, maybe I'm going to go and buy a bicycle tube at the bike shop. But that's going to create um a I'm doing business with them. I'm breaking that ice. I'm going to create a relationship. I'm going to have a conversation. I'm not just going to buy the tube. Right?
I'm going to be like, "Hey, it's a really nice store. How long has it been here? You know, how many bikes do you guys sell every month? Oh, this is so cool. I didn't even know that this was here." Right? You're having this conversation. That conversation is going to build um equity in your relationship. And so they might not need a new website, but you know what? They do
business with 25 other people in town and somebody's going to want something done and hopefully you're the name at the tip of their tongue. >> Yeah. I also think like co-working spaces, like throw that that on the list of places you might go. Um, specifically talk to the front desk people at co-working spaces. They know everybody there. They they're connectors usually.
Um, maybe ask them for a job, like, you know, tell them what's up. Tell them you need work. And um a lot I think if you find the right place and right people like people want to help I think but you got to ask and you got to be specific. >> You you got to get involved right? So I think that that is you know and that's something that AI can't do for you. AI
can't replace you. People want the relationship. They want that you know human in the loop experience. And so you know I I really drive back and I look at like where did the success of Mรฑana Nas really come from? It didn't come from Facebook ads. It didn't come from fancy tricks and stuff. It came from uh networking, shaking hands, going to meetings, getting on podcasts. Um, you
know, again, I'veorked with a lot of people that would say that, you know, that's my competition, but I usually get work from the relationships that should be with my competition because we have niches. We we have niches that are different than each other. So, we're able to share and refer work back and forth. >> Yeah. I I my experience has been like
that it's almost like less of a you don't it's not complex like getting work is about human relationships and we're all have a certain level of talent and ability at human relationships and I think like the more you lean into that and this is where last week we got uh we were yelling about marketing verse sales like I mean the one thing we're hitting
on 100% here is we are in a sales mentality when with all this We're saying how do we sell? We're not saying how do we get our brand out there? How do we market? Like the sales mentality, I think, is everything. And it's probably where businesses fail and succeed just generally speaking. Like if you take the organization as a whole, how big of a sales mentality do they
have? You know, it's probably it'd be an interesting study like to see like let's take every 20 person organization in the country and rate them on a sales how big a sales uh personality do they have? And I'm not talking about what they do. Like they could they could be a a fix it shop for your local automobile, you know, like but how big of are they do they
because sales people have an urgency about them that is it's a magnet. >> Yeah. I think you hit something very um important and I don't want to glaze over it. Sales is like that's the first thing. A lot of people say, "Oh, I'm going to build a website and I'm going to this and I'm going to market that and I'm going to do the other thing." And and we get all excited about all these
distractions, but distractions don't put a dime in your bank account. To me, like again, if I'm dropped off in a city with $200 in my pocket and a laptop, right? My number one goal is how many people can I meet? How quickly can I meet them? How many conversations can I have? And which of those conversations is going to lead to conversion? Each of those
conversations, I'm going to be identifying a need and supplying a solution. And if someone says, "Hey, that sounds like something I need." Or, "Hey, you need to talk to my nephew." Or, "You need to whatever." I'm going to follow that up. Like the number one thing is sales and revenue. See, I'm getting excited. I can hear it in my own voice. So, the number one thing is
revenue. As soon as I get that little bit of revenue, Toby, well, well, now I can go, "Okay, I've got revenue. Now, I can think about how would I market this and scale it and increase it and continue my sales." >> Yeah, maybe. I I don't even go there. I just go, "Let's go get >> I just keep selling." [laughter] the one thing you brought up that's really uh as we're as I'm thinking back
through this conversation today about the uh billion-dollar WordPress billionaire whatever um we haven't talked about marketing at all like that what didn't even occur to us as a thing to do >> no which >> uh instead we didn't mention websites we didn't mention like colors or logo and because when I think about this you've dropped somewhere you need work and this is this
person who maybe it's you listening and you're like, "Ah, I can't find work." Um, this is how I approach. I go, I find I would find the people and I hear someone say, "Hey, I really need a WordPress uh Woo Commerce site. Do you do that?" I would, you know, because I have that skill set, I say, "Yes, I do." "Do you have a website?" "Yes, I do, but um let me email it to you later."
>> [laughter] >> And now that I have their info, I have their contact info, I have what they need, I run home, I build a WooCommerce marketing site. I say, "Here's my website, um, and it's exactly what they need. It looks professional, you know, like I I wouldn't overthink the marketing piece until I have someone to sell to." Yeah, I'm um 100% I don't know
why I'm so focused on revenue lately because things have grown pretty decent, but um my last few lives and shows have really been based on like revenue. like we've got to get back to being focused on sales and revenue and all of this all of this other stuff like I'm hearing I'm seeing a ton from people in our space Toby with I'm going to vibe code this
and I'm making these tools and these plugins and this and I'm experimenting with this page builder and I'm doing and it's like okay that's great that you want to be at the threshold of advancement in our space like that's great if you want to be at the top of everything that's wonderful but I don't think the message today is driven to those people. I think the message today
is like don't waste time getting distracted by all these superfluous activities. WordPress by itself out of the box with like five or six key plugins. You can run an entirely profitable agency off of that and just get going. Just just create revenue, build projects, and get going. And you can always get to this other stuff when time comes. >> Thank you. That's a great way to segue
to the ending of our show here. Uh Kurt, how can people get in touch with you? Well, you can reach me at LinkedIn. I'm the only Kurt Vonan on LinkedIn. I encourage you to connect. Uh for business, uh we are mรฑana noms and mรฑana noms is the call sign for all of our socials and our.com. Toby, you >> I am on LinkedIn Toby and the last name is C R Y NS. You can find me at
themo.com. That's tmi gtm.com where we do WordPress stuff and SEO stuff. So, um thanks everyone for joining us today. always like to have you. Please like, send us emails, comments on any wherever you're watching or listening. Send us a comment if you have a question or an idea for a new show. Uh look forward to seeing you next week. >> Awesome. This is a fun one., Meetings Donโt Have to Suck, YouTube, 01kzrjgw3g6s71wjr5nze1shef.