Think Globally, Act Locally: Legal Tech That Works Across Borders
- David Langdon

- Jun 26
- 4 min read

“Think globally, act locally.” — Patrick Geddes
This timeless advice from Scottish planner Patrick Geddes opens Chapter 15 of Beyond the Features – and it’s especially relevant in a world where law firms and legal departments are increasingly operating across borders.
Whether you’re rolling out a new document management system across three regions, implementing time recording across ten offices, or deploying an AI-powered contract tool firm-wide, the same challenge arises: how do you create a unified strategy without losing sight of local reality?
Because here’s the truth: legal tech that works globally must fit locally.
The Risk of One-Size-Fits-All
On paper, a centralised global rollout looks efficient. One platform. One process. One set of dashboards. That’s the dream, right?
But reality has a habit of interfering.
What works at HQ can quickly fall apart elsewhere if you haven’t accounted for:
Local compliance requirements
Data residency and sovereignty laws
Language and character set limitations
Jurisdiction-specific billing practices
Cultural differences in tech adoption and legal process
If your global solution doesn’t flex where it needs to, you risk frustrating users, triggering compliance issues, and undermining the very efficiencies you set out to gain.
A Global Strategy With Local Wisdom
Geddes’ phrase – “Think globally, act locally” – is more than a soundbite. It’s a principle for sustainable, scalable delivery.
The best firms strike a balance between global consistency and local adaptability. That means building a legal tech strategy that:
Sets a clear global direction aligned to firm-wide goals
Develop and communicate a strategic vision that unites all offices under a shared purpose – whether that’s operational efficiency, improved client service, or compliance excellence. This direction should act as the North Star for all local implementations.
Involves local teams early to uncover risks and realities
Don’t wait until rollout to gather local feedback. Engage regional leaders, IT representatives, and end users from each jurisdiction at the design stage to understand regulatory nuances, pain points, and cultural preferences before they become roadblocks.
Selects modular, flexible platforms with built-in adaptability
Choose systems that allow for local configuration – such as custom fields, workflows, or integrations – without needing expensive custom builds. This ensures that each office can tailor the solution without breaking global alignment.
Delivers multilingual training and region-specific support
Training materials and user guides should reflect language needs, legal terminology, and working styles relevant to each location. Offering support that understands local context – not just technical issues – is key to driving adoption.
Builds in feedback loops from local users to global leads
Establish structured channels for collecting feedback from each region post-rollout. Encourage ongoing input so enhancements can be prioritised based on real-world use, not assumptions from head office.
Practical Example: Time Recording Across Jurisdictions
Imagine implementing a time recording solution across offices in Australia, Germany, the US, and Japan.
From afar, a single system makes sense. But what if:
Germany requires separate billing codes for regulatory reasons
Japan needs support for double-byte characters
Australia has time entry preferences that differ from the US
Local teams work differently, and training needs to reflect that
Without local input, the system may technically “work” — but adoption suffers, and compliance may be compromised.
The smarter move? Design the framework globally, then shape the implementation locally. That’s how you achieve both consistency and relevance.
Build the Stack – But Leave Room to Breathe
The goal isn’t to give every jurisdiction free rein to do whatever they want. That leads to tech sprawl and operational silos.
Instead, the goal is intentional flexibility – choosing platforms that allow for:
Local configuration without custom development
Multi-language and multi-currency support
Granular user permissions based on local needs
Central oversight with regional autonomy
That way, your global strategy has structure — but not rigidity.
Final Thought: Local Success Is Global Success
There’s nothing “small” about acting locally. In legal tech rollouts, the local experience is the real-world experience. If a system works well in the field, it contributes to global success. If it doesn’t, it becomes a global liability.
Geddes was right. If you want your global legal tech strategy to thrive — you need to design it with local reality in mind.
Need help balancing global vision with local needs?
You can book a free 30-minute discovery consultation via the button below. Let’s talk through your rollout plans and ensure your next implementation succeeds everywhere it matters – from headquarters to your most remote office.

Get the Book
If the topic covered in this blog post resonated with you…
You’ll find even more insight, structure, and practical guidance in Beyond the Features – a straight-talking resource designed to help law firms make smarter technology decisions, drive meaningful change, and avoid the common traps of transformation.
The book builds on ideas like those discussed here, offering frameworks, reflections, and actionable advice drawn from real-world experience.
Prefer digital? Get 25% off the PDF edition by using the code BTFEOFY25 when placing your order – valid until 30 June 2025.
Prefer print? The book is also available in paperback on Amazon.





Comments