Continuous Improvement SME
Microsoft
- Location
- Australia, Multiple Locations, Multiple Locations
- Work model
- On-Site
- Level
- Mid
- H-1B history
- 2,066 approvals (FY2023)
- Posted
- 2h ago
Skills
About this role
Overview
The Frontier Transformation Framework helps our customers become Frontier Firms: organizations where AI is part of the operating system the business runs on. The difference between a transformation and a one-off deployment is what happens after go-live. Without a deliberate improvement discipline, returns erode: adoption plateaus, agents drift, prompt libraries go stale, and high-value agents are starved while low-value ones persist. Continuous Improvement is the operating discipline that makes AI value compound over time rather than dissipate. The Frontier Transformation team is how the Microsoft Frontier Company, the organization this role sits within, delivers this: a small, senior human-agent team in which each member carries one of the Framework's eight capabilities into the customer, directs a set of digital co-workers to deliver at a scale headcount alone could not, and is designed to fade into a customer counterpart who can carry the work forward. We are seeking a Frontier Continuous Improvement SME to make AI value compound across strategic customer engagements. In this role, you will establish and run the Continuous Improvement Framework as a permanent operating rhythm, grounded in kaizen and strong facilitation, that redesigns and reruns workflows to outcomes. You will solve the last-mile problem, embedding what gets built into how work actually gets done through standard work, clear ownership, and an execution cadence that makes new ways of working stick, working directly with business owners, operators, champions, and the Value, Skilling, Change, and engineering leads. This is a role for people who are energized by making change hold rather than launching it, who can read measurement signals and turn them into the next round of improvement, and who believe a programme that ships once and leaves is just a release, not a transformation. You are designed to fade into a customer counterpart who owns the improvement rhythm after the engagement ends. If you are excited by turning AI deployments into value that compounds cycle after cycle, this role is for you.
Responsibilities
Understanding Customer/Partner Technical Environment Gathers and propagates customer/partner insights from a broad range of stakeholders as well as the main business sponsor that will help shape and form both the definition and ongoing execution of the project. Learns to identify and evaluate industry trends (customer industry verticals, information technology [IT] industry). Works with customer/partner stakeholders (e.g., Enterprise Architects, Security Team, Development Team, Operations Team) and business sponsor to socialize both the business solution and the project approach to determine if changes are needed to the business solution. Where the cost of change is accepted by the customer, shares this feedback with the project team and the broader account team to make the necessary adjustments using mechanisms such as updating the solution approach and projected costs in presales and change requests in delivery. Uses evidence-based approach to function as customer advocate and shares insights with Product Engineering teams and the business with a view to improving Microsoft technologies, products, services, and offerings such that they can better meet customer/partner needs. Architecture Design and Deployment Leverages a structured approach to architecture projects using existing methodologies (e.g., Waterfall, Agile, Iterative) that make use of existing reference architecture and established architectural styles and design patterns. Builds and maintains an architecture description document, an architecture decisions log, and a requirements/constraints traceability matrix to ensure the rationale for the business solution's Architecture is known and understood. Defines and documents the Architecture through an architecture description document, an architecture decisions log, and a requirements/constraints traceability matrix to