Who Should Make Decisions on the Client Side of an Outsourced Project

When attendees change every meeting, last week's decision gets reversed. Name a decision-maker, an owner and a user rep, and record decisions in one place.

Project Management··7 min read

When an outsourced project slips, the cause often turns out to sit on the client side, at the point where a decision stalled. A development team can build what has been settled, but what counts as settled has to be sorted out inside the client organization first.

When the Attendees Change Every Meeting

Q. We settled something at last week's review, and this week someone else raises it again. Why does this keep happening?

Because the person who decided last week and the person who joined this week are not the same. Last week a team lead attended and agreed to cut the filters on a list screen down to two. This week a division head attends and asks why there are only two. The team must now widen a screen it already narrowed, and work built on the narrower version is redone.

The problem is structural: nobody was fixed as the person who decides. When the people sitting at the review change every time, a decision stays valid only inside the meeting where it was made.

Q. Does that mean the CEO has to attend every meeting?

It does not. What is needed is one person with decision authority who sits at the same review, every week. That person does not have to hold the highest title. It only has to be someone the organization agrees to treat as the client's voice for this project. If the CEO cannot take the role, it is reasonable to name someone the CEO has delegated authority to, and to tell the development team about that arrangement.

When Opinions Arrive from Three Directions

Q. The CEO talks about direction, the project owner talks about details, and the business team asks for something else again. Whose words should the development team follow?

All three can be right. They simply speak at different levels. The CEO states a schedule and a goal: "We want the sales team using this within the quarter." The project owner states a detail: "Let people download the data in our existing spreadsheet format." The business team states a wish: "It would help if we could see it on a phone." When all three contact the development team separately, the requests collide, and the team has no authority to pick a winner.

For that reason, the channel for opinions should be reduced to one. The single point of contact with the development team is one day-to-day owner, and the person who sets priority among the requests is one decision-maker. Business opinions are not blocked; the owner collects and passes them on. It is safer to limit direct conversation between business teams and developers to sessions with a defined purpose, such as a demo or a usability check.

Q. If business opinions are collected and passed along, will the voices on the ground get filtered out?

That depends on how they are collected. When the owner receives an opinion, the owner writes one line for each: who raised it, in what situation, and what the difficulty is. The lines are organized weekly. When that list goes to the review, the decision-maker sees many people's input on a single page and chooses from it. When a request is not adopted, the reason is recorded in the same list, so there is an explanation ready to give back to the team that asked.

When Decisions Are Not Recorded Anywhere

Q. We clearly agreed on it in a meeting, but a month later nobody remembers.

What was said in a meeting is remembered a little differently by each attendee as time passes. The remedy is not difficult: record each decision in one place, even if it is a single line. A simple format is enough.

  • The date and the person who decided
  • One sentence on what was decided
  • One line on the earlier proposal, if there was one

Once these accumulate, the question "why did we do it this way?" can be answered immediately. The record needs to live in one place. Decisions scattered across chat, email and meeting notes take time to find, and nobody is sure which is final.

The client project portal we built is a place where the client checks progress and deliverables directly. With a portal like that, it is easy to keep the decision log in the same place. The tool does not have to be a portal: a single shared document works if everyone agrees to look at the same place. How to view progress in one place is covered further in Managing Outsourced Development and the Customer Portal.

The Three Roles

The client side needs three roles. One person can hold more than one role, as long as it is clear which role is speaking.

Role Responsibility At the review
Final decision-maker Sets priority and approves scope changes, and stands behind what is decided Attends every week at a fixed time and makes the decisions
Day-to-day owner Serves as the single channel to the development team and records decisions Prepares this week's items to confirm and the list of business opinions
User representative Speaks for the needs and difficulties of the team that will actually use the product Tries the product during demos and usability checks and gives feedback

One user representative per team is enough. This person aligns opinions inside the team first and then hands them to the owner.

The Order for Setting These Up

When contact first begins, four things are settled in order.

  1. Name one final decision-maker, and name one person who covers when that person is absent.
  2. Name the day-to-day owner, who handles all communication with the development team.
  3. Fix the day and time of the review to a slot the decision-maker can actually attend.
  4. Choose one place where decisions will be recorded.

How to convey requirements to a development team is covered in Communicating Requirements in Outsourced Development.

Frequently Asked Questions

Q. Our decision-maker is too busy to attend every week.

Keeping the session short is one option. If the items are organized in advance and only those needing a decision are raised, the review often takes 20 to 30 minutes. If even that is difficult, name a delegate and write down in a sentence what that person may decide.

Q. What if the decision-maker changes midway?

The change itself is not a problem. Hand over the decision record through the handover, and tell the development team when the change takes effect. If the record is in one place, the new decision-maker can read the reasons behind earlier decisions and take over from there.

Q. Do small projects need the roles separated too?

If only one or two people are involved, one person can hold several roles. Still, it is better to settle the final decision-maker and the place where decisions are recorded regardless of size. Both cost almost nothing, while rework without them is not small.

How Integrabbit Works

We at Cokee Corp. work under the name Integrabbit, building MVPs and business systems. The CEO, who has 15 years of development experience, confirms who the client's decision-maker and day-to-day owner are in the first week of each project. Much of the delay during development starts with blurred decisions. The review slot is fixed, and decisions are kept in the portal.

How to divide roles inside the client organization depends on its size and culture. If the roles are not settled yet, they can be sorted out together in a conversation about MVP development. The division described here is one reference point, and the judgment about what form suits your own organization rests with you.


If you are unsure how to divide roles on your side, bring your current situation and we will review it together in 30 minutes.

Book a free 30-minute review

Related Posts

Project Management

The Day After Launch: An Operations Checklist

Opening a service is where operations actually begin. The essential tasks an operator has to stay on top of — monitoring, backups, security patches, metrics — organized by priority.

#service operations#post-launch+3
Read More →