What If Your Team No Longer Shares Your Vision?
A lesson from Alexander at the Hyphasis
The modern dilemma
Pinning keeps chapter info in view on desktop. Unpinning returns it to the page flow. Chapter text always scrolls with the page.
This chapter scrolls with the page. Use the arrow keys or Page Up and Page Down to read. Press Tab to leave this reading area.
You lead a software team that built a useful reporting product. Customers now want a broader platform, and you believe expansion is how the company survives. The team helped win the first contracts. Now two senior engineers want to stop adding features until reliability improves. Others question whether the new product serves the customers they joined to help.
You have worked the same late nights and defended the team when deadlines slipped. Their resistance feels like a withdrawal from something you built together. Yet shared sacrifice does not tell you what they accepted: the original product, a temporary emergency, or a continuing obligation to expand.
Sharing risks can earn trust and make joint action possible. That trust does not authorize indefinite expansion: the next stage still needs a commitment people understand and can carry. Their resistance, in turn, does not establish that stopping is the best choice.
The disagreement could expose a limit your enthusiasm obscures. It could also underestimate a real commercial threat. People might even support expansion while doubting that you will honor promises to reduce the workload. Pausing might protect the product and lose the opportunity; proceeding might preserve the opportunity and damage the people needed to deliver it. Before trying to restore belief, you need to establish what has stopped being shared.
What If Your Team No Longer Shares Your Vision?
A story from history
Macedonian campaign in India · 326 BCE
- 326 BCE · Hyphasis
Eastward advance halts. Arrian 5.25–28.
- Decision and commemoration
Return announced; altars erected. Arrian 5.28.5–29.2.
- Subsequent campaign
Return west, then movement south and further fighting. Diodorus 17.95.3–96.5.
Pinning keeps chapter info in view on desktop. Unpinning returns it to the page flow. Chapter text always scrolls with the page.
This chapter scrolls with the page. Use the arrow keys or Page Up and Page Down to read. Press Tab to leave this reading area.
At the Hyphasis, the modern Beas, in 326 BCE, Alexander's eastward advance stopped. Arrian presents camp resistance and an officers' debate: Alexander invokes conquests and shared hardship; Coenus proposes returning and later recruitment. These are reported ancient speeches, not verbatim transcripts. Arrian, Anabasis 5.25–27, Chinnock translation.
The contrast matters even without knowing the speakers' exact words. In this narrative, recognizing what a leader has achieved does not settle what followers can undertake next. Coenus's position permits further ambition while questioning its immediate demands. That makes the dispute more precise than a contest between courage and weakness: the same enterprise can produce different judgments about when enough has been asked.
Diodorus supplies a material setting: worn equipment, losses, and heavy rain. He also describes an unsuccessful attempt to revive support through rewards and an address. His narrative supports examining practical burdens alongside persuasion; its details are transmitted claims, not a verified inventory. Diodorus, Library 17.94.1–5, C. Bradford Welles translation.
There was a serious case for continuing. Arrian's Alexander also warns that withdrawal could expose earlier gains. That possibility should prevent an easy verdict that the troops understood strategy and their king merely wanted glory. Arrian, 5.26.3–4. A future danger can be real while the proposed response exceeds present capacity. The decision requires comparing those risks, rather than treating either determination or fatigue as decisive evidence.
Arrian narrates renewed pressure, withdrawal to the royal tent, unfavorable sacrifices attributed to Ptolemy, then reversal. Arrian, 5.28–29. Edward Anson reads the sacrifices as allowing retreat under divine authority. Their political usefulness does not establish that the omens were fabricated; religious belief belonged to the decision's setting. Anson, “Religion and Alexander the Great,” pp. 59–60.
Even the familiar explanation is contested. Timothy Howe and Sabine Müller argue that a planned imperial boundary was later reshaped into a mutiny story; Anson disputes that reconstruction. We should therefore analyze the surviving confrontation without claiming access to Alexander's hidden plan. Howe and Müller, pp. 23–24, 34–38, Anson, p. 60 n. 37.
On the traditional reading, yielding recognized a constraint; it did not prove that abandoning further expansion was strategically best. Nor did changing direction end the army's exposure to war: Diodorus describes subsequent fighting during the southward campaign. Diodorus, 17.95.3–96.5. A revised destination can preserve a working force while leaving difficult obligations ahead.
Arrian 5.25–29 and Diodorus 17.93–96 preserve overlapping later accounts, with unknown dependencies. They are ancient testimony, not independent contemporary verification.
Arrian wrote in the second century CE. Speeches belong to literary historiography; their wording and historical substance remain debated. Hamburg university teaching edition, source and translator identification; Hammond, 1999, extract and n. 35.
Distinguishing a goal from the burden of its next stage is editorial analysis. Neither one speech nor a private motive is established as the sole cause of the halt. Vasileios Liotsakis argues that Arrian's indirect speech and source citations can emphasize a narrative turning point; those devices alone do not prove either doubt or authenticity. Liotsakis, 2023, pp. 168–171.
Sources & Further Reading
- Ancient / historical source
Book 5, chapters 25–29; printed pp. 306–316.
Full English translation. Arrian is a later ancient source; reported speeches are not verbatim transcripts.
- Source criticism & context
Source block “Arrian, 5, 25-28”; translation credited to Carl Cless.
Greek text and German translation with omissions. The page heading says Hydaspes; the source passage concerns the Hyphasis.
- Ancient / historical source
Book 17, sections 93–96.
Full English text hosted by the University of Chicago. Its relationship to other ancient accounts does not establish independent corroboration.
- Modern scholarship
Ancient History Bulletin 26, pp. 21–38; especially pp. 23–24, 31–38.
Full English PDF. The proposed planned boundary is a contested reconstruction, not an established fact.
- Modern scholarship
Karanos 5, pp. 51–74; especially pp. 59–61 and p. 60, note 37.
Full English PDF in a university repository. Offers a competing interpretation; political usefulness does not prove fabricated omens.
- Source criticism & context
Classical Quarterly 49.1, pp. 238–253; accessible extract and note 35.
Extract and bibliographic record only; the complete article was not read for this lesson. The online date of 2012 is not the publication year.
- Source criticism & context
Histos 17, pp. 144–181; especially pp. 168–171.
Full English PDF. Narrative analysis does not independently authenticate the reported events.
Discover the lesson
Pinning keeps chapter info in view on desktop. Unpinning returns it to the page flow. Chapter text always scrolls with the page.
This chapter scrolls with the page. Use the arrow keys or Page Up and Page Down to read. Press Tab to leave this reading area.
“A shared past does not settle the next commitment.”
- i
Find the boundary inside the refusal.
Ask people separately whether they dispute the purpose, the evidence for this opportunity, the schedule, or the burden. A team that supports the goal but cannot sustain the workload needs a different response from one that rejects the goal itself. Doubt that you will keep an agreement requires examining your decisions and follow-through. Ask what concrete change would make participation workable. If no feasible change would, the disagreement may require a decision about direction or roles.
- ii
Make the next commitment finite.
In the historical argument, previous achievement and continuing effort are connected but separable. Translate that distinction into a defined scope: which customers, which deliverables, what staffing, and when to review. A stopping condition makes agreement assessable. It also costs flexibility; a leader may reasonably accept that cost to learn whether support is real. A date alone means little if each deadline brings another unexamined extension.
- iii
Compare the cost of stopping with the cost of continuing.
Invite evidence from those carrying the work and from those responsible for the opportunity. Check error rates, unresolved dependencies, customer commitments, and recoverable capacity. Record which assumption would change the decision. A majority can identify a constraint without offering the best remedy; a leader can identify a threat without having a workable plan. Explain the choice you make and the burden it leaves with others.
A workplace is not a conquering army. Workers have different rights and avenues of exit; customers and affected communities also have claims that this leader–follower comparison cannot settle. Emergencies can require action before agreement. Repeated obstruction or a clear breach of duties may require accountability. This case does not make refusal a veto or establish that restoring enthusiasm would validate the plan.
Your decision
Choose what you would do. Each choice reveals a different perspective — none is simply right.
Imagine a launch whose window is closing while support work rises. You can preserve the timetable, pause to investigate, narrow the launch, or add a different delivery group. Each protects something valuable and puts something else at risk. The question is whether you can justify the next commitment with the people, evidence, and time actually available. What would make you change direction, and what would you need to know before asking the team to continue?
You run a fourteen-person software company. Two large prospective customers want a new workflow product, with a launch window eight weeks away. Your existing customers fund the business, but their support backlog has doubled during development. Several experienced employees want to stop the expansion; others favor it if support work is reduced. You believe the new contracts could fund the next year, but neither customer has signed. You have enough cash to maintain current staffing for six months. You must set a direction this week. What do you do?
