Short answer: In Uzbekistan's business culture, key decisions are often made by the owner, trust is built in face-to-face meetings, and disagreement is expressed with a polite "we'll think about it" rather than a direct "no". An ERP project that ignores this environment can fail even with a strong technical design. An Odoo team from Dubai or any other country has to learn this environment first; Deep Vision, an Odoo Gold Partner in Tashkent, works inside it every day.
Business culture rarely comes up when companies choose an ERP. Yet in practice an Odoo implementation is more often delayed by misunderstandings between people than by technology: the right person was not in the meeting, an objection was never voiced, go-live was scheduled for the week before a holiday. This article covers the features of Uzbek business culture that shape an ERP project, how to account for them and how to check whether your Odoo implementation partner understands them.
How does business culture affect an ERP project?
Business culture is the set of unwritten rules that decide how a company makes decisions, builds trust, voices disagreement and plans its time.
An ERP project is mostly communication. PMI's 2013 Pulse of the Profession study found that US$135 million is at risk for every US$1 billion spent on projects, and 56% of that, US$75 million, is at risk because of ineffective communications; about half of unsuccessful projects relate to ineffective communications as well (PMI). And communication always happens inside a particular culture.
A simple example: a consultant holds a workshop with storekeepers. Everyone nods, nobody asks questions, and the consultant writes down "agreed". Two weeks later it turns out the storekeepers did not accept the new process; they just did not think it appropriate to object in front of their department head. Nobody lied; the two sides read the same conversation differently.
Which features of Uzbek business culture matter for ERP?
These affect every phase of the project:
- Decisions revolve around the owner: in many companies the founder or director has the final word, so they need to attend the key meetings.
- Family businesses: relatives work in different roles, and the formal org chart does not always match real influence.
- Trust is built in person: the first important agreements are usually made in the office, over tea or on the shop floor.
- Respect and hierarchy: the views of managers and experienced staff carry special weight, and changes that bypass them are hard to accept.
- A polite "no": objections often sound like "let's think about it" or "we'll come back to this later".
- The holiday and fasting calendar: the month of Ramadan, Ramazon and Qurbon Hayit, Navruz and other holidays change the rhythm of work.
- Long relationships: companies value working with a good partner for years, and recommendations travel by word of mouth.
None of this is a weakness: it is a strong culture built on trust and responsibility, and the ERP project has to follow its rules.
Why does a team from Dubai or any other country need time to learn this environment?
An Odoo specialist from Dubai, Europe, Turkey, India, Russia or Kazakhstan may be a strong professional in their own environment. Skill is not the issue. A team from a different business environment first has to learn how decisions are made here, who has real influence and when "we'll see" means "no". It also usually works remotely for much of the project.
A Microsoft study of 61,182 employees found that firm-wide remote work made collaboration networks more static and siloed, with less synchronous and more asynchronous communication, which the authors say may make it harder to acquire and share new information (Nature Human Behaviour). Where trust is built face to face, that effect is even stronger. So a foreign team faces built-in disadvantages: it cannot be on site, in context and accountable the way a local team is.
How do Ramadan, Navruz and holidays affect the project schedule?
The go-live date for Odoo has to respect the calendar. During Ramadan the rhythm of the working day changes, and meetings close to iftar are inconvenient. Before Hayit and Navruz retail traffic rises, so switching tills to a new system at that time is risky. Month-end and year-end reporting keeps the accounting team busy.
A local team plans around these dates by default; a schedule drawn up from another country can easily land go-live right before a holiday.
How do you spot an objection behind "we'll think about it"?
To avoid missing polite disagreement:
- Discuss key processes with each department separately, in small groups.
- Make it easy to raise concerns: ask "what could be inconvenient in this process?"
- Confirm agreements in writing and revisit them at the next meeting.
- Ask managers and key staff for their view first, and do not work around them.
- Test with real data before go-live: a problem seen in practice reveals an objection that was never said aloud.
According to Prosci, 88% of projects with excellent change management met or exceeded their objectives, against only 13% with poor change management (Prosci). Understanding the culture is the foundation of change management.
How can you check whether a partner understands your business culture?
Ask yourself:
- Did the partner come to your office or site for the first meeting?
- Did they identify the meetings where the owner must be present?
- Did they ask about holidays and seasonal peaks before proposing a go-live date?
- Can they talk to your storekeeper, cashier and accountant in their language?
- If there is a disagreement, with whom and where will you resolve it face to face?
- Will the partner still be in the same city, next to you, after go-live?
If many answers are "no", part of the timeline will go into repairing communication. Detailed criteria: how to choose an Odoo partner in Uzbekistan. Common pitfalls: 7 ERP implementation mistakes.
How does Deep Vision work within this culture?
Deep Vision is an official Odoo Gold Partner with an office in Tashkent, at Shahrisabz ko'chasi 25. Our Odoo partner page lists 7 certified experts, 20+ client references and 89% customer retention (the Gold minimum is 80%, Odoo).
- We hold the first meeting and the diagnostics at your premises, and we can get to you quickly when needed because we are in the same city.
- Key decisions are agreed with the owner or director in a single meeting.
- We talk to your staff in Uzbek and Russian, using their own terms.
- The team includes experienced specialists who know industries and finance, not only programming.
- Diagnostics come first, then an estimate split into clear phases, and the go-live date is chosen around holidays and seasons.
More about us: why Deep Vision. An example result: a case that cut costs from $30,000 to $11,000. How we work locally: Odoo implementation in Tashkent. Service details: Odoo implementation. To discuss your project, send a brief.
Frequently asked questions
Does business culture really affect a technical project?
Yes. An ERP project is made of conversations and decisions. A team that does not understand who decides, and how, will reach agreement with the wrong person.
Does the owner have to attend every meeting?
No. But decisions on goals, budget and key processes should be made by the owner or by someone they have empowered.
Can we go live with Odoo during Ramadan?
Yes, but the schedule should follow the working rhythm. Launching a new till system in retail right before Hayit is usually not recommended.
Can't a foreign team learn the culture?
It can, but it takes time, and that time is usually paid for by your project. A local team already lives in this environment.
Sources
- PMI — The High Cost of Low Performance: The Essential Role of Communications
- Nature Human Behaviour — effects of remote work on collaboration
- Prosci — change management and project success
- Odoo — Deep Vision partner page
- Odoo — partner tiers
Let's talk about your project in person: send a brief or call +998 77 093 00 07.