Forem: Kinetic Goods

The Meeting You Can't Skip

Kinetic Goods — Sat, 25 Apr 2026 03:38:35 +0000

Every professional has one. A meeting that shows up on the calendar and you dread going. Not because it's long or badly run — just because you can't see the point. You're not presenting, not deciding, not learning. You're attending.

The meeting you can't skip. And why it feels like a waste.

Why These Meetings Exist

These meetings usually exist for one of three reasons:

The organizer needs you there for optics. Not for input — for presence. Someone wants the meeting to look populated, or to signal that a decision has buy-in from all relevant parties.

The information sharing requires your presence. Not because you have a unique perspective — because the organizer doesn't trust async updates to reach you effectively.

No one has ever questioned whether it should exist. It's on the calendar. It always has been. Therefore it continues.

The Cost

You sit in the meeting. Your camera is on or off. You may or may not speak. You definitely won't remember what was discussed an hour after it ends.

And you can't skip it — not because of the meeting itself, but because of what skipping would signal.

How to Handle It

Opt out where possible.

Send a message: "I have a conflict, can I get the notes instead?" This works when the meeting truly doesn't need you.

Add value when you're there.

Ask the question that nobody wants to ask. Surface the thing that everyone's thinking but not saying. If you're going to be in the room, be present.

Push back on recurring meetings that don't serve you.

Once. Politely. "I notice I've been in this meeting six times and haven't contributed. Can we consider making it async or removing my attendance?"

The meeting you can't skip is often a meeting that could be skipped. Make the case for why yours doesn't need to be a meeting.

The Meeting That Changed How You Think About Meetings

Kinetic Goods — Sat, 25 Apr 2026 03:07:03 +0000

There was a meeting that changed how you think about meetings. Not because it was good — because it was bad in a way that taught you something.

Maybe it was the meeting where someone asked a question that exposed a flaw in the plan. Or where the debate went somewhere unexpected and you realized the original decision was wrong. Or where the meeting ran so long and went so badly that you thought: "We need to do this differently."

The meeting that changed how you think about meetings. You walked in with one set of assumptions and walked out with different ones.

What Changed Your Assumptions

You expected the meeting to confirm something. Instead, it revealed something.

The meeting wasn't about the stated topic. It was about something deeper — how decisions actually get made, who actually has power, what the team actually cares about. You saw the gap between the official process and the real one.

You expected the meeting to produce a decision. Instead, it produced a question.

After the meeting, you had a better question than you had before. Not a decision — a question. And that question turned out to be more useful than the decision would have been.

You expected the meeting to be a formality. Instead, it was a workout.

Your thinking got exercised. Not in a comfortable way — in a way that made you reconsider something you'd assumed was settled.

What You Learned

Meetings aren't just about outcomes. They're about revealing how things work — or don't.

The next time you're in a meeting that feels formative, pay attention. Not just to what's happening, but to what it's teaching you about how decisions, power, and information flow in your organization.

The meeting that changed how you think about meetings is always the one you didn't see coming.

The Meeting That Won You a Promotion

Kinetic Goods — Sat, 25 Apr 2026 01:36:44 +0000

Not every meeting is a waste. Sometimes a meeting is where you make an impression that changes your trajectory.

The meeting that won you a promotion. You know the one. You said something that landed. You made a connection with someone who mattered. You contributed something that got noticed — and then followed you into your next conversation, your next review, your next role.

The meeting that won you a promotion. And what you did differently in that meeting.

Why One Meeting Can Change Things

Most work happens in obscurity. You do your job, you produce output, you hope someone notices. The meeting is one of the few places where your thinking becomes visible to people who can act on it.

In the right meeting, with the right people, one idea can reframe a conversation. One question can demonstrate expertise. One observation can mark you as someone who sees what others don't.

That's the meeting that won you a promotion. Not because you worked late, but because you showed up and mattered.

What You Did Differently

You were prepared in a specific way.

Not just knowing your stuff — knowing what the meeting needed. You came with context about the decision, the people, and the stakes.

You spoke at the right moment.

Not the first to talk, not the last to agree. You said the thing that the room needed to hear exactly when it needed to be said.

You made it about the work, not about you.

You weren't performing your competence. You were contributing to something that mattered. The room felt that difference.

What It Teaches

Visibility requires being seen in the right moment. You can't manufacture those moments, but you can be ready when they arrive.

The meeting that won you a promotion wasn't planned. But when it happened, you were prepared to make it count.

The Meeting That Made You Question Your Career

Kinetic Goods — Sat, 25 Apr 2026 01:06:03 +0000

There are meetings that test your patience. Then there's the meeting that makes you question whether you're in the right career.

Not because of what was discussed — but because of how it was discussed. The casual dismissal of ideas you'd championed. The decision that ignored your expertise. The peer who got promoted despite producing nothing while you stayed invisible.

The meeting that made you question your career. It's not about the meeting. It's about what the meeting revealed.

What These Meetings Reveal

Where you stand in the hierarchy.

Some people get consulted in meetings. Others get informed. The meeting makes the power structure visible even when org charts don't.

How much your voice actually matters.

You speak up. Your idea gets a nod, then shelved. Someone else says the same thing an hour later and it becomes the plan. The meeting reveals whether your input shapes decisions or just fills airtime.

What the organization actually values.

The meeting shows you what gets rewarded. Not what's on the walls or in the all-hands — what's actually reinforced in the room. Who gets heard. Whose work gets used. Who gets promoted.

When the Meeting Is a Signal

If one meeting made you question your career, it's a data point. If every meeting makes you question it, it's a pattern.

The pattern tells you something. Either you're in the wrong organization, or you're expecting something the organization isn't designed to give.

Neither is a reason to quit immediately. But both are reasons to pay attention.

What to Do With the Signal

Name it to yourself.

"I just had a meeting where my input was ignored and someone else got credit for my work." Say it out loud. The signal gets clearer when you state it plainly.

Assess whether it will change.

Is this a one-time thing or a structural pattern? Has anything changed in the last six months, or is this exactly how it's always been?

Make a plan.

If the pattern won't change, you have three choices: find a different position in the organization, find a different organization, or accept that this is what it is and stop fighting it.

The meeting that made you question your career is asking a question. The meeting itself isn't the answer.

The Meeting That Tested Your Patience

Kinetic Goods — Sat, 25 Apr 2026 00:36:10 +0000

Every professional has a meeting that tried their patience. Not the boring ones — those you can mentally check out of. The ones that tested your patience were different.

The person who wouldn't stop talking. The tangent that derailed the entire agenda. The question that was asked and answered three times. The debate that went in circles without any resolution.

The meeting that tested your patience. And what it revealed.

What Patience Reveals

Patience is a finite resource.

You came in with a full tank. By minute thirty, you were running on empty. The person who kept talking — you stopped listening. The debate that went nowhere — you started mentally drafting your next email.

Patience gets consumed. And some meetings are designed to consume it faster than others.

Your tolerance changes with context.

A meeting you would have sat through easily last week becomes unbearable when you're already overwhelmed. The same meeting, the same content — but your capacity to absorb it has changed.

This isn't weakness. It's resource management.

Patience revealed what's wrong with the meeting.

If you found yourself testing your patience, something was wrong with the meeting. Either it was badly designed, badly run, or simply shouldn't have happened at all.

What You Can Do

Leave.

Not rudely — but you can say "I have another commitment" and exit. Your time has value. You don't have to stay in a meeting that's wasting it.

Redirect.

If you're the one running the meeting and you see patience thinning, change the format. "Let's take this offline." "Let's get to the decision and revisit the rest later."

Flag it.

After the meeting, say: "I noticed the meeting felt longer than it needed to be. Can we talk about shortening future versions?"

Patience is information. What you're feeling is a signal about the meeting's quality. Don't ignore it.

The Meeting That Revealed a Leadership Vacuum

Kinetic Goods — Sat, 25 Apr 2026 00:06:19 +0000

Something happens in meetings that have no clear leader. Not nothing — worse. Something happens that exposes the gap where leadership should be.

People talk over each other. Nobody intervenes. The loudest voice wins, regardless of the quality of the idea. Important topics get dropped. Unimportant topics get debated. The meeting runs over, and nobody knows why.

The meeting that revealed a leadership vacuum. It's not a meeting problem. It's a leadership problem.

What a Leadership Vacuum Looks Like

No one intervenes when things go off track.

The discussion drifts. Someone raises a concern that derails the agenda. Nobody says "let's stay on topic." Nobody redirects.

Decisions get made by whoever speaks last.

There's no process for deciding. The last person to make a strong case wins — not because their idea was best, but because no one was managing the decision-making.

The meeting doesn't end — it dissipates.

Instead of wrapping up with clear decisions and next steps, the meeting just... stops. People start checking their phones. Someone says "we should probably wrap up." Everyone leaves without knowing what happened.

Why It Happens

Leadership vacuums happen when the person who called the meeting isn't willing to lead it. They scheduled it, but they're not driving it. They're reacting to what happens instead of shaping what happens.

Or when the meeting has too many stakeholders and no one has the authority to make final calls. Everyone has input rights, but no one has decision rights.

How to Fill It

Before the meeting, know who's driving.

The person who called the meeting is responsible for its outcome. That person opens it, guides it, and closes it. If they can't, they assign someone else who can.

During the meeting, name the vacuum.

If you see it happening, say: "It sounds like we need someone to drive this. I'll take that role — here's the agenda." Leadership isn't waiting to be assigned. It's stepping up.

After the meeting, assess.

Ask: "Did we have a clear decision owner? Did the meeting have a clear end?" If not, the next meeting needs a different format.

A meeting without leadership is a meeting that wastes everyone's time. Leadership isn't optional in meetings — it's the job.

The Meeting That Became Your Job

Kinetic Goods — Fri, 24 Apr 2026 23:35:34 +0000

At some point, a meeting became your job. Not officially — not on your org chart, not in your title. But it showed up in every calendar, every status report, every decision that involved your team.

Someone had to own the recurring sync. Someone had to track the action items. Someone had to follow up when things slipped. And somehow, that someone became you.

The meeting that became your job. Often without a conversation about it.

How This Happens

You attended once and never left.

The first meeting, you were invited as a participant. You contributed. Someone said "this should be on [your team's] plate." And now it's yours.

You organized it before anyone asked.

You saw a need and filled it. You set up the recurring meeting, you sent the agendas, you wrote the notes. It worked, so it stuck.

You were the only person who cared.

The meeting had a purpose. Nobody else remembered to do it. You did. And now you're the person who does.

When It Becomes a Problem

The meeting became your job when it takes time you don't have, produces output you don't own, or creates accountability for things you can't control.

You're tracking action items for people who don't report to you. You're following up on decisions you didn't make. You're running a meeting that would continue without you — but only because you've made yourself indispensable.

How to Fix It

Make it official or make it stop.

If the meeting is worth having, assign ownership explicitly. Not "someone should track this" — "Sarah owns this meeting and its outputs." If it's not worth owning, cancel it.

Transfer the meeting.

If you've been running it, find someone else to own it next quarter. Don't just hand it off — hand it off with the full context of why it exists and what it produces.

Protect your time.

A meeting that became your job can consume the time you need for the job you actually have. Audit your recurring meetings and ask: which ones do I actually need to be in?

The meeting that became your job is usually a meeting that grew beyond its original intention. Trim it back to what it actually needs to do.

The Meeting That Started With a Wrong Assumption

Kinetic Goods — Fri, 24 Apr 2026 23:06:15 +0000

It started with "we all know why we're here."

What followed was an hour of discussion based on a premise nobody had verified.

"We're cutting the budget." The team spent two meetings discussing how to cut the budget. Except nobody had decided to cut the budget. It was a rumor that took on momentum.

The meeting that started with a wrong assumption. Everything that followed was built on a foundation that didn't exist.

Why Wrong Assumptions Spread

No one questions the premise.

When someone starts a meeting with "since we're all aligned on X," the room accepts X without examination. Questioning feels like disruption. It isn't — it's rigor.

Assumptions feel like facts.

"We need to restructure the team." Not "we've decided to restructure" or "we're considering restructuring." Just "we need to" — as if the decision has already been made and the only question is how.

By the time you realize, it's too late.

You've built plans around the assumption. You've had conversations with stakeholders. You've made commitments. Even when you discover the assumption was wrong, reversing it feels more painful than continuing.

How to Catch Wrong Assumptions

At the start of any meeting, ask: "What's the decision we're making today?"

If the answer is "we're not making a decision, we're just discussing" — you're probably in an assumption-based meeting.

When someone says "we all know X," say: "Actually, let me verify that."

Not confrontationally. Just: "Can we confirm that X is actually the case before we move forward?"

Distinguish between decisions and hypotheses.

"We're doing X" is a decision. "We need to do X" is a hypothesis wearing a decision's clothes.

The meeting that started with a wrong assumption produces a plan that's wrong before it begins. Verify first.

The Meeting You Want to Skip But Can't

Kinetic Goods — Fri, 24 Apr 2026 22:35:21 +0000

There's a meeting on your calendar that you dread. Not because it's badly run — it's not. Not because the topics are boring — they're not. You just don't want to be there.

This is the meeting you want to skip but can't.

It might be a status update from a team you don't directly work with. It might be an all-hands where you don't have anything to contribute. It might be a recurring sync that was valuable once but now feels like an hour you could spend better.

You're not alone. Everyone has these meetings. And most people just show up and wait for them to end.

Why You Feel This Way

The meeting served its purpose.

The original reason for the meeting made sense. But at some point, the reason faded. The meeting kept happening anyway — inertia, not intent.

You're not getting anything from it.

Not information, not decisions, not relationships. It's an hour that produces nothing for you.

You're not contributing anything to it.

If you disappeared, nothing would change. You show up, you wait, you leave.

When Skipping Is Wrong

You should go to the meeting if:

Your presence matters for the decision
Your team is counting on you to represent their interests
You're the owner and it would model bad behavior to skip

When Skipping Might Be Right

If none of those conditions apply, ask yourself:

Can this meeting be shorter? And if so, can you leave early without consequences?

Can this meeting be async? Can you get what you need from the notes without attending?

Can this meeting be skipped? Can you send a message saying "I won't be there, but I'm aligned based on the recap"?

The meeting you want to skip but feel obligated to attend is a signal. Either the meeting needs to change, or your relationship to it needs to change.

The meetings worth attending are the ones where you're genuinely needed. Everything else is optional.

The Meeting Where Nobody Knew What to Do Next

Kinetic Goods — Fri, 24 Apr 2026 22:05:45 +0000

The meeting ended. The decisions were made. The action items were assigned. Everyone knows what they need to do.

Except they don't.

You check in a week later. Nothing happened. You ask why. People give you answers that don't quite make sense. They thought someone else was doing it. They weren't sure the decision still stood. They didn't know if they had the authority to start.

This is the meeting where nobody knew what to do next.

Why Action Items Don't Become Actions

The assignment was vague.

"We'll take the next step on the vendor review." Not "I'll have a shortlist by Friday." Not "Sarah owns the vendor evaluation by April 30."

The decision wasn't explicit.

"We decided to move forward with this approach." Move forward how? With what resources? By when?

The authority wasn't clear.

Is this person actually empowered to do this? Or are they just the person who volunteered to take notes?

What Makes an Action Item Real

A real action item has four elements:

Name: Who owns it. Not "marketing" — Sarah.

Verb: What they're doing. Not "vendor review" — evaluate vendors and present recommendation.

Date: When it's due. Not "when we get to it" — Friday, April 30.

Clarity: Everyone knows this is real, not optional.

How to End Every Meeting

After every meeting, say this:

"Let's confirm the action items. Who owns what, and by when?"

If you can't answer that question, the meeting isn't over. You have more work to do before everyone leaves.

The meeting where nobody knew what to do next is a meeting that ended too early.

The Meeting You Walked Into Already Decided

Kinetic Goods — Fri, 24 Apr 2026 21:35:30 +0000

You get to the meeting ten minutes late. Someone waves you over. The meeting is already in progress.

A decision is being announced. You weren't part of the pre-meeting where this got figured out. You don't know the context. You don't know the tradeoffs. You just hear the conclusion.

"We decided X." You weren't there for the deciding.

This is the meeting you walked into already decided. And it's one of the most common experiences in organizations.

Why Decisions Happen Before the Meeting

Decisions happen before meetings because:

The real work happens in conversations. The meeting is where decisions get ratified, not where they get made. The actual negotiation, the actual tradeoffs, the actual agreement — that happens in the hallway, in the chat, in the one-on-one.

Some decisions don't need everyone. When the right people have already talked, bringing in more people is theater. The decision has been made. The meeting is the closing ceremony.

Power protects itself. Sometimes decisions happen before the meeting because the people making them want control. They're not interested in input. They're interested in validation.

Why Being Left Out Matters

You were left out because either:

Your presence wasn't needed to make the decision (the pre-work was sufficient)
Your presence wasn't wanted (you would have complicated things)

Either way, the meeting you walked into was already a performance. The decision was made. The decision you're hearing is the script.

What You Can Do

Ask to be in the pre-meeting.

If the real decisions happen before the meeting, ask to be part of that conversation. "I'd rather be in the room where this gets figured out."

After the meeting, ask the question that matters.

"So what would have happened if I'd been in the room? Would the decision have been different?"

If the answer is no, you weren't left out — the meeting just wasn't for you.

If the answer is yes, you have a problem.

If you keep walking into decided meetings, change your position.

Either get included in the pre-work, or accept that the decisions aren't yours to influence. Waiting until the meeting to have input is too late.

The Meeting You Stopped Taking Notes In

Kinetic Goods — Fri, 24 Apr 2026 21:05:11 +0000

At some point, you stopped taking notes. Not because you were engaged — because you had given up.

The meeting was going somewhere, but you couldn't see where. The decisions weren't getting named. The action items weren't getting captured. Every time something important was said, you made a mental note — and then watched it evaporate by the next meeting.

So you stopped trying.

This is the meeting you stopped taking notes in. And it's the clearest signal that the meeting itself has a problem.

Why Note-Taking Stops

Note-taking stops when the meeting has no clear direction. If you can't predict what's going to be decided, you can't prepare for it. And if you can't follow what's happening, you stop trying to capture it.

It also stops when notes don't matter. If you've been in meetings where you took notes and nothing happened to them, you learned that notes are theater. Just like everything else in that meeting.

What the Absence of Notes Tells You

The absence of notes tells you the meeting has lost its purpose. People aren't expecting decisions, so they're not tracking them. People aren't expecting follow-through, so they're not documenting it.

The meeting continues to happen. It consumes time. But it's not doing anything.

How to Fix It

Name decisions out loud as they happen.

When a decision gets made, say it: "So we've decided to go with Option A. Sarah owns the implementation plan, due Friday." Now everyone has something to write down.

Review notes at the end of every meeting.

"Here's what we captured. Does this match what we agreed to?" This creates accountability for both the decisions and the note-taking.

Act on what you capture.

If the notes from last week's meeting are still sitting in someone's inbox unread, the notes aren't the problem. The follow-through is.

A meeting worth having is worth taking notes in. If you've stopped taking notes, ask why — then fix the meeting.