MeetFika

Management evaluation series · Part 2 of 4

Managing to Preference: The Most Common Management Mistake

6 min read·By Romeo·

In part one we looked at the three lenses managers use to evaluate people: performance, preference, and perception. Of the three, managing to preference is the one I see most often. Most managers aren’t unfair or careless. Preference is hard to spot in yourself.

Nobody wakes up planning to grade their team on personal taste. They believe they’re evaluating quality, professionalism, effectiveness, strong work. The trouble is that a lot of the standards we lean on aren’t standards at all. They’re preferences. And when preference gets mistaken for performance, feedback starts to feel inconsistent, subjective, and almost impossible to act on.

Every manager has preferences

Start with the uncomfortable truth: every manager has preferences, and so does every leader you have ever worked for. We pick them up from our own experiences, our wins and failures, the mentors we had along the way. We form opinions about communication, documentation, meeting participation, project management, presentation style, decision-making, responsiveness, and a dozen other things.

Over enough time, those opinions become so familiar that we stop noticing them as opinions. They start to feel like plain truths about how work should be done. That is exactly where the problems begin.

How preferences become invisible

Picture two managers. The first prefers concise communication, where a one-paragraph update is ideal. The second wants the full picture: context, background, rationale, supporting detail. Neither is wrong, and both styles can work well.

Now move one person from the first manager to the second. The exact communication style that earned praise last quarter starts drawing criticism this quarter. The person didn’t change. The expectations did. The hard part is that managers tend to forget their preferences are personal. We assume everyone shares them, or worse, that everyone should.

The PowerPoint problem

Here’s the example I keep coming back to. A manager asks for a report. The person spends days gathering data, validating it, running the analysis, and organizing the recommendations. They hand over a comprehensive workbook. The manager is disappointed, because they pictured a slide deck. The person is confused, because they did the work.

Who failed? A lot of managers point at the report’s author. I don’t. The assignment got done, the information was delivered, the recommendations were there, the outcome was achieved. The manager is reacting to format, not result. That’s preference, not performance.

You can’t reasonably hold someone accountable for an expectation you never communicated.

If you wanted a slide deck, the fix is to say so. That isn’t lowering the bar. It’s setting one.

Where new managers struggle most

This shows up most with new managers, and the reason is almost flattering. Many first-time leaders get promoted because they were strong individual contributors. They were organized, knowledgeable, good at getting things done. Then they step into management and, without realizing it, start measuring their team against themselves.

The questions form quietly. Why didn’t they approach it the way I would have? Why didn’t they organize it the way I would have? Why didn’t they make the call I would have made? Those feel reasonable, but they’re usually the wrong questions. The job isn’t to become a copy of you. The job is to reach the outcome. Some of the best people I’ve worked with solved problems in ways I never would have considered, and insisting they work exactly like me would have capped both their growth and their results.

The difference between standards and preferences

Not every preference is a problem, and some absolutely should become standards. The line comes down to communication and consistency. “Executive presentations should use our standard template” isn’t a personal quirk anymore once you’ve said it. It’s an established expectation everyone can see, which makes accountability fair.

The issue was never that managers have preferences. It’s that so many of them stay unspoken, and people can’t meet a requirement they never received. A useful gut check before you give critical feedback: have I communicated this expectation clearly enough that a reasonable person would know it exists? If the answer is no, the gap may be communication, not performance.

The check-in is the natural place to make those expectations explicit, while there’s still time to act on them. If you want a structure for that conversation, here’s how to run a 1:1. Writing the expectation into a shared agenda both of you can see — the way MeetFika keeps it — is what turns a private preference into a standard your teammate can actually meet.

The hidden cost

Managing to preference does more damage than one awkward feedback conversation. Over time it reshapes how a team works. People become less focused on outcomes and more focused on pleasing the manager. Instead of asking “what’s the best solution,” they start asking “what solution will my manager like,” and that’s a meaningful difference.

It collides directly with psychological safety, too. A team can be told it wants different perspectives while quietly learning that only perspectives resembling the boss’s are actually welcome. People pick up on the gap fast. They get cautious, stop offering alternatives, and start optimizing around the manager instead of the mission. The strongest managers I know hold enough structure to set clear expectations while leaving enough room for people to decide how to meet them. It’s a hard balance, and it’s where some of the best leadership happens.

A simple test

When you feel dissatisfied with someone’s work, try one question: if a different person delivered this exact outcome using a different approach, would I still be unhappy? Sometimes the answer is yes, and the issue is performance. The work was incomplete, the quality was off, the outcome missed.

Other times the outcome is fine, and what’s bothering you is that you would have done it differently. When that happens, you have a decision to make. If the preference matters, communicate it. If it doesn’t, let it go. That choice is a real part of the discipline of managing.

Preference isn’t the enemy

None of this argues for erasing your preferences, which would be impossible anyway. Preferences create consistency and culture and help teams work together. The goal is to recognize them, then decide which ones should stay preferences and which should become explicit expectations. If something matters, communicate it. If it matters consistently, standardize it. If it shapes evaluations, document it. The clearer you separate preference from performance, the fairer and more effective your leadership becomes.

FAQ

What does "managing to preference" mean?

Managing to preference is evaluating work against your own personal style and habits rather than against the result. You expected a slide deck and got a workbook, or you wanted a one-paragraph update and got three pages. The outcome may be fine, but the work is judged on whether it matched your taste.

Why is it the most common management mistake?

Because preferences rarely feel like preferences. Over time they start to feel like universal standards, so a manager holds someone accountable for an expectation that was never communicated. It is especially common with new managers, who tend to evaluate their team against how they themselves used to work.

How do I tell a preference from a real standard?

A standard has been communicated and is applied consistently. "Executive presentations use our standard template" is a standard because everyone knows it exists. An unspoken expectation that lives only in your head is a preference. The test: have I communicated this clearly enough that a reasonable person would know it exists?

Should managers get rid of their preferences?

No, and you could not if you tried. Preferences help create consistency and culture. The goal is to recognize them, then decide whether a given preference should stay a preference or become an explicit, communicated expectation. That distinction is what separates fair accountability from arbitrary accountability.

Say it once, then keep it visible

Half of managing to preference is just never writing the expectation down. MeetFika gives you and your teammate one shared agenda you both add to before each check-in, so expectations get said out loud and follow-ups carry forward instead of living only in your head.

Free to start.

Start Free — your first check-in is 2 minutes away