UK

United Kingdom · Technology and data · Lead (8-12 years)

Lead Solutions Architect

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Lead Solutions Architect plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Also at another level: the Senior Solutions Architect job description.

Upskilling a team in this role? Talk to us

  • Experience bandLead (8-12 years)
  • Direct reportsNo direct reports
  • Reports toDirector of Architecture
  • UK framework levelUsually a manager, or the deepest specialist in a team

Also advertised as Staff Solutions Architect · Principal Architect (Technical Lead) · Senior Technical Design Lead

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 2 Certificate In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards
EAL Level 2 Diploma In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards
EAL Level 2 Certificate in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards
EAL Level 2 First Certificate in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards
EAL Level 2 Diploma in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards
EAL Level 2 First Diploma in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 7 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Leading a team in Engineering EAL Level 2 Certificate In Engineering Technologies

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
AI Governance Fluency using AI responsibly
Sustainability Fluency building care for people and planet into the work
Systems Fluency seeing the whole picture
Start my Lead Solutions Architect plan, free

2AI and this work

Will AI change your work as a Lead Solutions Architect?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • AI-Assisted Architectural Design & Validation
  • Sustainability & Green Software Architecture
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Lead Solutions Architect plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Lead Solutions Architect plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A Lead Solutions Architect designs technical solutions that solve business problems and connect the work of several teams.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Cloud Platforms (AWS/Azure/GCP) Expert

Designing multi-service, resilient, and cost-optimised architectures across at least two major cloud providers. Deep expertise in serverless (Lambda, Functions), containers (EKS, AKS, GKE), advanced networking, and security services.

Infrastructure-as-Code (Terraform/CloudFormation) Advanced

Authoring complex, modular, and reusable Terraform modules from scratch. Implementing state management, workspaces, and integrating IaC into CI/CD pipelines. You'll set the standards here.

Containerisation & Orchestration (Docker/Kubernetes) Expert

Designing and troubleshooting complex Kubernetes deployments (Operators, service meshes like Istio/Linkerd). Configuring Helm charts, managing cluster autoscaling, and implementing robust security policies for containerised workloads.

CI/CD & Automation (GitLab CI/GitHub Actions/Jenkins) Advanced

Architecting complete CI/CD pipelines, integrating security scanning (SAST/DAST), quality gates, and advanced automated deployment strategies (Blue/Green, Canary). You'll be improving our software delivery lifecycle.

Observability & Monitoring (Datadog/Prometheus/Grafana) Expert

Defining and implementing enterprise observability strategies. Configuring custom metrics, alerts, and distributed tracing. Building comprehensive dashboards that correlate system performance with business KPIs across multiple services.

Diagramming & Documentation (Lucidchart/Miro/Draw.io) Expert

Creating comprehensive High-Level (HLD) and Low-Level Design (LLD) documents, Architectural Decision Records (ADRs), and detailed sequence diagrams. You'll establish and maintain architectural documentation standards.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Technology Stack Selection for New Project Suggest options to senior architect, implement chosen stack under supervision. Propose and justify a specific stack for review, implement independently. Design and recommend the optimal stack, lead implementation, consult Director for major deviations from enterprise standards.
Cloud Resource Allocation & Cost Optimisation Identify potential cost savings for review, apply basic cost-saving configurations. Implement cost-optimisation strategies for specific services, report on savings. Design cost-efficient architectures, identify and propose significant cost-saving initiatives, manage budget for specific workstreams.
Architectural Design for Critical Business Service Assist in documenting components, conduct research on specific patterns. Design a sub-component of a critical service, create LLDs. Lead the HLD/LLD for a critical service, present to peers for review, make technical decisions within scope.
Mentorship & Team Development Seek guidance from senior team members, participate in learning initiatives. Provide informal guidance to new joiners, share knowledge in team meetings. Formally mentor 1-2 junior team members, lead internal tech talks, contribute to onboarding materials.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Architectural Adherence Rate
Percentage of projects that stick to the approved architectural design without significant, unapproved deviations.
Target · >90%

In Q2, 18 out of 20 major projects launched followed the agreed-upon HLD/LLD, hitting a 90% adherence rate.

Cloud Cost Optimisation Impact
Measurable reduction in cloud infrastructure costs for solutions you've designed or optimised.
Target · Identify and deliver £50K+ in annualised savings for your domain

Redesigned the data ingestion pipeline, reducing its monthly AWS spend by £4,500, leading to £54,000 in annualised savings.

Reduction in Architectural Flaw Incidents
Decrease in major production incidents directly attributable to architectural design flaws within your domain.
Target · 20% year-over-year reduction

After implementing a new microservices pattern, incidents related to inter-service communication failures dropped from 5 in Q1 to 1 in Q4.

Time-to-Market for New Capabilities
The average time it takes for a new, architecturally significant feature or service to go from concept to production within your domain.
Target · Reduce by 15% through design efficiency

Standardised API gateway patterns, cutting the average deployment time for new external integrations from 6 weeks to 5 weeks.

Cross-Team Architectural Alignment
How well different engineering teams understand and agree on the architectural direction for shared components or services.
  • Regularly sought out by multiple team leads for architectural guidance
  • designs are adopted without significant pushback
  • fewer 'shadow IT' solutions appearing
  • positive feedback in anonymous team surveys about architectural clarity.
Technical Debt Prevention
Your ability to foresee and design around potential technical debt, balancing short-term delivery with long-term maintainability.
  • Architectural Decision Records (ADRs) clearly articulate trade-offs and future implications
  • fewer 'temporary' solutions becoming permanent
  • proactive identification of refactoring needs before they become critical
  • positive feedback from engineering leads on the forward-thinking nature of designs.
Mentorship & Knowledge Sharing Impact
The positive influence you have on the technical growth and understanding of junior architects and engineers.
  • Junior team members proactively seek your advice
  • you're running regular tech talks or workshops
  • engineers you've mentored take on more complex design tasks
  • positive feedback from mentees about your guidance and support.
Strategic Influence & Buy-in
Your ability to influence senior stakeholders (Product, Engineering VPs, Finance) to adopt your architectural recommendations.
  • Your proposals are regularly approved and funded
  • you're invited to early-stage strategic planning meetings
  • you can clearly articulate the business value of technical investments
  • senior leaders reference your architectural insights in their own presentations.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Big, Gnarly Problems

You'll be handed some of our trickiest technical challenges—think integrating legacy systems with new cloud-native platforms, or designing highly scalable data processing pipelines. You get a real kick out of unpicking these complex puzzles and seeing your solutions bring order to chaos.

Spending a week deep-diving into a complex data migration challenge, sketching out several potential solutions, and then leading the discussion to pick the best path forward.

Shaping the Future of Technology

This role isn't about maintaining the status quo. You'll be at the forefront of defining how we build things, what technologies we adopt, and what our technical landscape looks like in 2-3 years. You'll influence our technical roadmap and standards.

Researching a new serverless technology, running a proof-of-concept, and then presenting a compelling case to engineering leadership for its adoption across the organisation.

Mentoring & Guiding Others

You'll spend a good chunk of your time helping other engineers and architects grow. This means reviewing designs, offering advice on tricky technical decisions, and generally being a go-to expert who helps unstick people. Seeing others succeed because of your guidance is a big win for you.

Sitting down with a junior architect to walk them through a complex cloud networking design, explaining the 'why' behind each decision, and helping them refine their own diagrams.

What frustrates people
  • The 'Solution looking for a problem': Being pressured to adopt a trendy technology (e.g., 'We need to use blockchain!') that doesn't actually solve a real business need.
  • Architectural Drift: Seeing a carefully designed system slowly degrade as teams take shortcuts or introduce 'temporary' fixes that become permanent.
  • The Sales-Engineering Gap: Sales promising a client a feature that's technically infeasible or requires a massive re-architecture, leaving you to be the bearer of bad news.
  • Inheriting the 'Mystery Box': Being assigned to modernise a critical legacy system with no documentation, no tests, and all the original developers long gone.
  • 'Just a quick question...': Constant interruptions that derail deep thinking time, making it impossible to focus on complex design work.
  • The Battle for Refactoring: Continuously having to justify the business value of paying down technical debt to product managers who only want to ship new features.
  • Being the 'Ivory Tower' Architect: The perception from engineering teams that you're disconnected from the day-to-day realities of coding and operations.
What this role does not give you
  • A purely hands-on coding role (you'll code, but it's not your main gig).
  • A predictable, unchanging technical landscape (things move fast here).
  • A role where you can avoid difficult conversations with senior stakeholders.
  • A job where every single one of your designs makes it to production exactly as intended.

8Who you work with

This role directly influences the technical direction and strategic choices for significant parts of our business. Your designs will dictate how scalable, secure, and cost-effective our solutions are, impacting our ability to innovate and compete. You'll often be the person who helps us avoid major technical debt or costly re-architecture down the line, which, frankly, saves us millions in the long run.

Inside the business
  • VP of Engineering and Engineering Leads
  • Product Management Directors
  • Head of Infrastructure & Operations
  • Security & Compliance Teams
  • Finance Business Partners (for cost modelling)
Outside the business
  • Key Technology Vendors (e.g., AWS, Azure, GCP account teams)
  • Strategic Integration Partners
  • Industry Peer Groups (for best practice sharing)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • A minimum of 8 years of hands-on experience in software development, DevOps, or infrastructure engineering, with at least 3-5 years specifically in a Solutions Architect role.
  • Proven track record of designing and delivering complex, scalable, and resilient technical solutions in a cloud-native environment.
  • Demonstrable experience leading architectural discussions and influencing technical direction across multiple teams without direct authority.
  • Strong understanding of at least one major cloud provider (AWS, Azure, or GCP) at an expert level, with good familiarity with another.
  • Experience mentoring junior technical staff and contributing to their professional development.
  • A portfolio or examples of High-Level Designs (HLDs), Low-Level Designs (LLDs), or Architectural Decision Records (ADRs) you've personally authored.

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Distributed Systems Design & Resilience Engineering

As our systems become more distributed and complex, designing for extreme resilience, fault tolerance, and graceful degradation becomes paramount. You'll need to master patterns for chaos engineering, self-healing systems, and multi-region deployments to ensure continuous availability.

Chaos engineering principles and tools (e.g., Chao · Active-active vs. active-passive multi-region arch · Circuit breakers, bulkheads, and retry patterns fo · Eventual consistency models and distributed transa · Designing for data sovereignty and disaster recove

  • This quarter: Dive deep into a specific resilience pattern (e.g., circuit breakers) and apply it to a current design. Read 'Designing Data-Intensive Applications'.
  • Next quarter: Research chaos engineering tools and propose a small-scale experiment for a non-critical service.
  • Within 6 months: Design a multi-region disaster recovery strategy for a critical service, considering RTO/RPO objectives.
  • Within 9 months: Lead a technical deep-dive on a complex distributed systems concept for the wider architecture team.

Quick win: Start incorporating explicit resilience requirements and failure modes into your HLDs. It forces you to think about what happens when things go wrong.

Platform Engineering & Developer Experience (DevEx)

Organisations are increasingly building internal developer platforms to accelerate delivery and improve developer satisfaction. As a Lead Architect, you'll be instrumental in designing these platforms, ensuring they provide self-service capabilities, standardised tooling, and a fantastic developer experience, ultimately boosting productivity.

Internal Developer Platform (IDP) design principle · Self-service infrastructure and application provis · Golden paths and paved roads for development teams · Measuring developer experience (DevEx) metrics · Toolchain integration and standardisation

  • This quarter: Read up on 'Team Topologies' and 'Platform Engineering' concepts. Understand the motivations behind IDPs.
  • Next quarter: Identify a pain point in our current developer workflow and propose a platform-based solution.
  • Within 6 months: Contribute to the design of a new self-service capability for our internal platform, focusing on ease of use.
  • Within 9 months: Advocate for specific tools or standards that would significantly improve our developer experience, backing it with data.

Quick win: Start talking to engineering teams about their biggest frustrations with our current development environment. Their feedback is gold for platform design.

11Staying current once you are in

What people here do to keep up
  • Regularly attend industry conferences (e.g., AWS re:Invent, KubeCon, QCon) to stay abreast of emerging technologies and best practices.
  • Actively participate in online technical communities, forums, or open-source projects to share knowledge and learn from peers.
  • Dedicate time each week to 'spike' new technologies or architectural patterns through personal projects or internal PoCs.
  • Seek out mentorship from more senior architects or technical leaders, both internally and externally.
  • Contribute to internal technical blogs, run workshops, or present at company-wide tech talks to share your expertise.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

AI-Assisted Architectural Design & Validation

AI is rapidly changing how we design and validate systems. Tools are emerging that can suggest architectural patterns, identify potential flaws in designs, and even generate code snippets based on architectural specifications. Architects who can use these tools effectively will be significantly more productive and accurate.

  • Generative AI for code and infrastructure template
  • AI-powered architectural pattern recognition
  • Automated threat modelling using AI
  • AI for performance and scalability simulation
  • Ethical considerations in AI-driven design

Sustainability & Green Software Architecture

Organisations are increasingly focused on environmental impact. Architects will need to design systems that are not only performant and cost-effective but also energy-efficient. This involves making conscious choices about cloud regions, resource utilisation, and data transfer patterns. It's becoming a key NFR.

  • Carbon footprint of cloud computing
  • Energy efficiency of different compute types (CPU
  • Data transfer and storage optimisation for reduced
  • Choosing 'green' cloud regions
  • Measuring and reporting software carbon emissions

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Cloud Architecture Patterns
  • Solution Design & Documentation (HLD/LLD/ADR)
  • Well-Architected Frameworks & FinOps
  • Enterprise Integration Patterns
  • Security by Design (DevSecOps)
  • Data Architecture & Governance

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Senior Solutions Architect (Internal Promotion)

    3-5 years as Senior Architect

    Skills to master

    • Deepen expertise in a specific technical domain, consistently lead large project architectures, mentor junior team members effectively, and begin to influence cross-team technical decisions.

    You're ready to move on when

    • Consistently delivers high-quality HLDs/LLDs for complex projects.
    • Proactively identifies and addresses architectural risks.
    • Recognised as a go-to expert for a specific technology or domain.
    • Successfully mentored 1-2 junior team members to take on more responsibility.
  2. 2

    Principal Engineer / Staff Engineer (External Hire)

    8-12 years in engineering roles

    Skills to master

    • Strong background in hands-on coding and system design, with a proven ability to architect large-scale systems. Excellent communication and leadership skills, even without formal management authority.

    You're ready to move on when

    • Demonstrable experience leading the technical design of major software components or systems.
    • Strong track record of influencing technical direction and driving best practices within engineering teams.
    • Deep understanding of software architecture patterns and trade-offs.
    • Excellent problem-solving skills for ambiguous technical challenges.
  3. 3

    Technical Lead / Engineering Manager (Internal or External)

    5-8 years in a technical leadership role

    Skills to master

    • Experience managing small teams of engineers, defining technical roadmaps, and making strategic technical decisions. A desire to move into a broader architectural design role.

    You're ready to move on when

    • Successfully led an engineering team to deliver complex projects.
    • Strong technical vision and ability to translate it into actionable plans.
    • Experience with resource planning and project management.
    • Desire to focus more on system design and less on direct people management.

15Where this role leads

The long view: This role can lead to a Chief Architect or CTO position, or to a Head of Engineering role, shaping technology decisions at a wider level.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Lead Solutions Architect is actually changing.

Where it leads

Roles this leads to

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Leading a team in Engineering, worked against Lead Solutions Architect.

Leading a team in Engineering Level 2

Applied to your work in Lead Solutions Architect

The objective of this unit is to equip learners with an understanding of the roles, responsibilities, knowledge, and skills required to effectively lead a team in an engineering environment. Learners will explore how to manage team workloads, allocate tasks, and contribute to achieving team goals through effective leadership practices.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Lead Solutions Architect plan, free
See Your Progress Grow Illustration
Lead Solutions Architect
  • Cloud Architecture Patterns
  • Solution Design & Documentation (HLD/LLD/ADR)
  • Well-Architected Frameworks & FinOps
  • Enterprise Integration Patterns
  • Security by Design (DevSecOps)
  • Data Architecture & Governance
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Lead Solutions Architect is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Principal Solutions Architect

    3-5 years in Lead Solutions Architect role

    Level 5 (Principal/Manager)

    • Multi-Domain Architectural Vision Defining the architectural vision for major business domains or product lines, not just individual programmes.
    • Strategic Vendor Management Evaluating new platform services for enterprise adoption and managing top-level vendor relationships.
    • Advanced FinOps Strategy Driving significant, measurable reductions in platform Total Cost of Ownership (TCO) through strategic initiatives.

  2. Director of Architecture

    4-6 years in Lead Solutions Architect role (often after a stint as Principal)

    Level 6 (Director/VP)

    • Enterprise Technology Strategy Owning the technology strategy for an entire business unit, including budget management (£2M-£10M+).
    • M&A Technical Due Diligence & Integration Leading the technical assessment and integration of acquired companies.
    • Industry Thought Leadership Representing the company's technical vision externally and influencing industry trends.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a big chunk of an architect's job involves sifting through information, translating complex ideas, and keeping documentation up-to-date. Imagine if you could cut down on those repetitive tasks and focus more on the truly strategic, creative design work. That's where AI comes in.

For a Lead Solutions Architect, AI isn't about replacing you; it's about giving you superpowers. You'll use these tools to automate the tedious bits, get to insights faster, and communicate your vision more effectively, freeing you up to tackle the really tough architectural challenges.

Automated Diagramming & Documentation

Feed your Terraform code, cloud configurations, or even code repositories into AI tools that automatically generate and update system architecture diagrams. No more manually dragging boxes around in Lucidchart after every change. It'll also help you draft those HLDs and LLDs, getting you 80% of the way there, letting you focus on the nuanced details.

Proactive Cloud Cost Optimisation

Use AI-powered FinOps platforms to analyse our cloud billing data, spot anomalous spending spikes before they become a problem, and get specific recommendations for right-sizing or shutting down unused resources. This replaces hours of manual spreadsheet analysis and helps you keep our cloud budget in check, making you a hero to Finance.

Rapid PoC Code Generation & Validation

Need to quickly test a new technology or design pattern? Use AI coding assistants (like GitHub Copilot) to generate boilerplate code for Proof-of-Concept applications in minutes. This means you can validate new approaches much faster, without getting bogged down in syntax, and focus on the core architectural question you're trying to answer.

Executive Summary Synthesizer

Got a lengthy, highly technical design document or a stack of Architectural Decision Records? Feed them into an AI model and ask it to generate a concise, one-page executive summary. You can tell it to focus specifically on business impact, risks, and costs, drastically reducing the time you spend translating deep technical concepts into business-friendly language for leadership presentations.

Common questions

Common questions

How do you become a Lead Solutions Architect?

Common routes in include Senior Solutions Architect (Internal Promotion) (3-5 years as Senior Architect), Principal Engineer / Staff Engineer (External Hire) (8-12 years in engineering roles) and Technical Lead / Engineering Manager (Internal or External) (5-8 years in a technical leadership role). Times vary with prior experience.

Where can a Lead Solutions Architect progress to?

This role can lead on to Principal Solutions Architect (3-5 years in Lead Solutions Architect role) and Director of Architecture (4-6 years in Lead Solutions Architect role (often after a stint as Principal)), depending on the skills you build.

What new skills matter most for a Lead Solutions Architect?

Increasingly, AI-Assisted Architectural Design & Validation and Sustainability & Green Software Architecture. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

17Where to go from here

Other roles at Level 5

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.
This job at other levels
More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built as a Lead Solutions Architect transfer across industries that rely on complex technology, including finance, e-commerce, healthcare and public services. Translating business needs into scalable technical solutions is in demand everywhere.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Lead Solutions Architect plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.