You asked for something, it didn't happen, and you need to follow up

You are not bad at this, and they are not slacking. That dread is worth listening to: the real work happens up front. A follow-up feels like a confrontation only when the first ask was a suggestion in disguise.

Move it upstream. Before you set the next expectation, open that person's results and turn to Understanding Styles. Read their working style and the notes on trust and friction.

• Accelerator: give the finish line and deadline in one line, then step back. A check-in like "what's in your way?" reads as help, not a leash.
• Analyst: spell out what "done" looks like and why it matters. A check-in like "let's poke holes together" reads as rigor, not doubt.
• Harmonizer: set it warmly and in private, and name why it matters to the team. A check-in like "how's it feeling, what do you need?" reads as care.
• Pragmatist: hand them the scope to own and one concrete outcome. A check-in like "where's it landing?" respects that the work is theirs.

Write the expectation down before you say it, in their language. One line: the what, what "done" looks like, and the check-in you set together.

For an Analyst: "I need the pricing model by Thursday, with the assumptions listed so we can defend them. Let's take ten minutes Wednesday to poke holes in it."

Read it back. If it still sounds like a favor, it is a suggestion. Firm up the finish line and the definition of done until no reasonable person could miss it.

Now the part that kills the dread. Because you set the check-in up front, the follow-up is a meeting you both booked, not an ambush. You arrive with one written expectation and a check-in that reads as support, not surveillance.