An approach to enterprise legal leadership
I build the systems that make sound legal judgment useful across the enterprise.
Clear ownership. Workable processes. Reliable information. A legal function connected to the decisions the business needs to make.
Every company has a way of making decisions, assigning resources, handling exceptions, and following through. Legal has to work within that system.
The Integrated Legal Operating Model (ILOM) connects people, decision rights, workflows, information, and tools so that legal judgment reaches the business at the right time. It defines how a request enters the function, who owns it, how risk is evaluated, when an issue escalates, and how a decision becomes action.
The ILOM Toolkit comprises a matter and work register, a connected document and knowledge repository, communication and coordination, and shared work management. These are capabilities, independent of the specific tools selected. Governed dashboards use KPIs and KRIs to direct attention; internal Legal reports and enterprise reporting draw from the same controlled records. Interfaces with Finance and the other business functions define ownership, timing, escalation and accepted handoffs.
Technology supports that design. The starting point is the business: its strategy, pace, people, and tolerance for risk. A growing company establishing its first legal function will need a different structure from a mature enterprise bringing separate teams together.
The practical test: can people get the help they need, understand who decides, and see what happens next?
These are the parts I look at together when building or improving a legal function.
Define the legal team’s responsibilities, priorities, staffing, and relationship with business leadership. Establish which work belongs inside the organization and where specialist counsel is needed.
Business value: Clear accountability and resources matched to the company’s needs.
Establish intake and triage, assign responsibility, and connect contracts, disputes, investigations, and other legal issues to the appropriate workflow. Preserve important dates and commitments as work moves between teams.
Business value: Fewer lost requests, avoidable handoffs, and surprises.
Translate risk tolerances into usable playbooks, approval authority, and escalation paths. For contracting, that can mean standard positions, acceptable fallbacks, and a clear route for exceptions.
Business value: Routine work moves efficiently, with senior attention directed to consequential choices.
Connect policies, compliance obligations, and enterprise risks to named owners, practical controls, reporting, and follow-through. Clarify where Legal, Finance, Compliance, and business leaders each have a role.
Business value: Leadership can see who is responsible and whether action has occurred.
Establish a matter owner, strategy, budget, milestones, and expectations for outside counsel. Connect spending and exposure reporting to the decisions leaders need to make.
Business value: Better visibility into priorities, cost, and developing risk.
Connect a reliable issue register with the supporting document record. Design reporting and select technology around the workflow. Apply AI where it can improve the work, with appropriate information controls and human review.
Business value: Less time reconstructing events and a stronger basis for judgment.
An illustrative dispute workflow
The sequence below illustrates the operating model. Each step connects a legal responsibility to a business decision and a record of what happened.
A claim arrives through service of process, a business contact, or another intake channel. The matter is recorded, relevant documents are linked, and the response deadline is captured.
What requires immediate action? The register identifies the issue, source, deadline, and person responsible for the next step.
The responsible lawyer evaluates urgency, likely exposure, preservation needs, and business impact. The right business partners become involved early.
Who owns the matter, and does it meet an escalation threshold? The assessment and required actions are documented.
The team decides how to respond, whether outside counsel is needed, and what the work should cost. Counsel receives a defined scope and expectations.
What approach best serves the business? A strategy memo, budget, responsibilities, and milestones establish the working plan.
Work proceeds against the plan. Deadlines, developments, and spending are tracked. Changes in exposure or strategy reach the appropriate decision-maker.
Has something changed enough to require a new decision? Updated assessments, approvals, and commitments preserve the reasoning.
Legal assesses exposure and provides its recommendation to Finance. Finance owns the reserve decision within the company’s accounting process. Leadership receives reporting appropriate to the matter’s significance.
What does leadership need to know now? Legal’s assessment, Finance’s action, and the reporting history remain connected.
The outcome, final cost, and remaining obligations are recorded. Lessons feed back into contracts, business practices, controls, or future litigation strategy.
What should change? Assign an owner to any corrective action and track it through completion.
For a contract, the trigger may be a sales request and the decision an exception to standard terms. For compliance, it may be a new obligation and the work of assigning a control owner. The subject changes; ownership, authority, information, and follow-through remain essential.
Timothy A. Whitley · Legal leadership in practice
Nine principles. Four disciplines.
Learning informs the next decision.
Integrity. Compassion. Personal accountability.
The four disciplines organize development and application. The management cycle is SEE → ALIGN → DECIDE → EXECUTE → LEARN → ADAPT. The principles apply throughout.
I would build around the organization’s needs, preserving what works and addressing the points where work breaks down.
Understand strategy, interview the people doing the work, trace common requests, and identify unclear decisions, recurring delays, and material risks.
The output: an assessment and a prioritized roadmap.
Clarify the mandate, assign owners, establish intake, capture key obligations, and define decision and escalation authority.
The output: a working foundation with clear responsibilities.
Develop playbooks, connect the register and document record, establish counsel expectations, and align reporting with business and financial processes.
The output: repeatable workflows and useful management information.
Review adoption, delays, cost, and outcomes. Remove unnecessary steps, refine controls, and introduce automation where it earns its place.
The output: an operating model that evolves with the company.
Reporting should help leaders decide where to act. Measures depend on the business and the maturity of the function.
| Leadership question | Useful visibility |
|---|---|
| Where is work getting stuck? | Request age, contracting cycle time, approval delays, and repeated handoffs. |
| Are we spending where it matters? | Budget variance, forecast spend, staffing needs, and outside counsel performance. |
| What could require a decision? | Material exposure, emerging issues, recurring exceptions, and approaching deadlines. |
| Are our controls working? | Overdue actions, policy exceptions, missed escalations, and recurring incidents. |
| Is the system helping people? | Adoption, business feedback, rework, and whether corrective actions are completed. |
The purpose is to make decisions better informed and execution more accountable. Measures should change behavior in useful ways.
ILOM brings together disciplines developed across different roles and business needs.
At DIRECTV, I built the enterprise litigation organization and risk governance function following separation from AT&T, connecting matter oversight, outside counsel, legal operations, and executive reporting.
At AT&T, I consolidated three litigation organizations into one enterprise function, redesigning structure, reporting, workflows, and resource allocation.
In AT&T’s National Business and Global Enterprise Sales organization, I led legal support for leadership teams responsible for more than $35 billion in annual revenue. Contracting playbooks, fallback positions, and collaborative workflows helped connect legal judgment to sales execution.
Six years on Southwestern Adventist University’s Board of Regents, including governance, bylaws, and finance committee service, also informs how I think about oversight, responsibility, and the information a board needs.
Legal leadership, in practice
A team that understands the company. Decisions made at the right level. Work carried through. Information that helps leadership act.
Connect with Tim Return to my executive profile →