There's a thing that happens in digital work that should be obvious once you see it, but somehow keeps surprising people. The title "account manager" means almost nothing without context, because it's doing double duty in most organizations. And that double duty is quietly creating a whole category of miscommunication that doesn't need a name because everyone just assumes it's normal.
One account manager is a relationship manager. They're the person a client knows. They're the connective tissue between what the client needs and what the organization can deliver. They sit in meetings where they're actually listening, remembering details, understanding priorities. They know the client's world well enough to anticipate what matters next. They call when something matters. They remember conversations.
The other account manager is a delivery coordinator. They're managing the account from the inside, which sounds similar until you realize it's a completely different job. They're tracking timelines, making sure projects stay on schedule, communicating with whoever's actually doing the work, managing scope creep, handling the logistics of keeping things moving. They rarely see the client. The client might not even know their name.
These aren't the same thing. But organizations keep treating them like they could be, or worse, like they should be. One person. One title. Both jobs.
The friction shows up immediately if you pay attention. The relationship manager needs flexibility because relationships require it. They need to say yes to conversations, to understand nuance, to adapt when a client's priorities shift. The delivery person needs structure because delivery requires it. They need to manage dependencies, protect timelines, say no when scope doesn't fit. These aren't compatible modes of operation, but they're being asked to happen inside the same person.
So what actually happens? Sometimes the relationship manager is good at it and the delivery falls apart because they're spending energy on understanding the client instead of organizing the work. Sometimes the delivery person is excellent at logistics and the client relationship feels hollow because nothing's happening at that level. Sometimes both things suffer because the person's splitting their brain between two incompatible jobs.
The organizations that have figured this out don't necessarily call it out explicitly either. They just structure it differently. Maybe there's a relationship manager who owns the client connection and a project manager who owns the delivery, and they talk to each other constantly. Maybe the titles are different so nobody's confused about what they're actually supposed to be doing. Maybe the person doing relationship work isn't also the person tracking whether the website's going live on Thursday.
What's strange is how rarely this gets addressed directly. It's like everyone assumes it's just how account management works. That person's just juggling two jobs. That's their job, juggling. But juggling isn't really a sustainable way to deliver either good relationships or good work. It's a way to deliver mediocre versions of both.
The interesting question isn't whether these two functions should exist. They should, because clients need both relationships and delivery. The interesting question is why so many teams keep assuming they can live in one person's calendar, under one title, without explicitly acknowledging that they're actually completely different things. Once you see the gap, it's hard to unsee it. And once you see it, you start noticing how many projects are struggling not because the person isn't capable, but because they're being asked to be two people at once.