
One of the key billable accounts, this project required deep understanding of UI/UX design and a thorough operational mindset.
400+
page designs
250+
design QAs
17
members
Give the requirement to the onshore team, and are responsible for the final approval on the designs before the pages go-live.
Based in Seattle, USA, collaborate directly with the SMs, gather the requirement & streamline the design process.
Based in Bengaluru, India, create pages as per requirement, and collaborate with the offshore team.
With teams based in both locations, collaborate with both Onshore/Offshore design teams to launch the pages after strict QA process.
Despite geographical distribution, clear communication maintains clarity, speed, and accountability. Two-way loops ensure seamless flow of ideas and feedback between teams, enabling rapid iteration and a unified vision.

Process Flow
Page Designing
Requirement gathering
Onshore team/leads gets feedback/requirement from MSFT and the shares them via Workfront.
Design
Offshore leads assign it to respective designers. Designers work on the tickets in accordance with MSFT design guidelines & themes.
Design Review
Offshore lead reviews the work, suggesting changes as needed. The Content team conducts a detailed copy review. Review rounds continue with stakeholders until the final design is achieved.
Handoff
Post review all related assets are shared as HO folders to dev team for production. Post-production, the designs are sent for QA.
Quality Assessment
Ticket Allocation
Dev team segregates Design QA tickets by pod and product, creates them in Workfront, and assigns to the offshore lead for delegation.
QA Review
Designers compare preview pages with Figma to find issues. Each bug is documented with descriptions and screenshots linked to the parent ticket.
Issue Resolution
Authors address the reported bugs. Designers close the ticket once issues are resolved, triggering a final review by the offshore lead and a follow-up review by the onshore lead as needed.
Launch
The review cycle continues until all views meet MSFT SM standards. Once approved, the page is queued for go-live. Further changes after launch are fast-tracked.
Transitioning into the role of Design Lead from Sr. Designer, I currently lead one out of the three design pods handling various Microsoft products. With a 3-member team at my disposal, my pod is responsible for the page designs & QAs of key products like M365, Copilot, Teams, Viva & Events. Some of my key responsibilities involved:
Initiatives
I actively identified production and design gaps, built accelerator tools, and created design guidelines to improve speed, consistency, and efficiency. From conceptualizing new ideas to establishing smoother workflows and scalable processes, my initiatives helped teams work faster, smarter, and more collaboratively.

Copilot Guidelines
To support Copilot design revamp, initiated theming guidelines to standardise designs and reduce errors.

Designer Onboarding
Quick step-by-step guide to understand the flow of work in a pod. Designed for newly onboarded designers.

HO Fastrack
Implemented a faster, more accurate handoff process for production, making the process ~20% faster.

Content checklist
Drafted 14 checkpoints to minimise copy error within the team and increase overall output accuracy.

Team Retrospective
Initiated internal feedback loop to proactively identify gaps and opportunities in the team.

ACOM Page Designs
We ideated new ACOM page designs and used Adobe Firefly to create stunning visuals.


One of the key billable accounts, this project required deep understanding of UI/UX design and a thorough operational mindset.
400+
page designs
250+
design QAs
17
members
Give the requirement to the onshore team, and are responsible for the final approval on the designs before the pages go-live.
Based in Seattle, USA, collaborate directly with the SMs, gather the requirement & streamline the design process.
Based in Bengaluru, India, create pages as per requirement, and collaborate with the offshore team.
With teams based in both locations, collaborate with both Onshore/Offshore design teams to launch the pages after strict QA process.
Despite geographical distribution, clear communication maintains clarity, speed, and accountability. Two-way loops ensure seamless flow of ideas and feedback between teams, enabling rapid iteration and a unified vision.

Process Flow
Page Designing
Requirement gathering
Onshore team/leads gets feedback/requirement from MSFT and the shares them via Workfront.
Design
Offshore leads assign it to respective designers. Designers work on the tickets in accordance with MSFT design guidelines & themes.
Design Review
Offshore lead reviews the work, suggesting changes as needed. The Content team conducts a detailed copy review. Review rounds continue with stakeholders until the final design is achieved.
Handoff
Post review all related assets are shared as HO folders to dev team for production. Post-production, the designs are sent for QA.
Quality Assessment
Ticket Allocation
Dev team segregates Design QA tickets by pod and product, creates them in Workfront, and assigns to the offshore lead for delegation.
QA Review
Designers compare preview pages with Figma to find issues. Each bug is documented with descriptions and screenshots linked to the parent ticket.
Issue Resolution
Authors address the reported bugs. Designers close the ticket once issues are resolved, triggering a final review by the offshore lead and a follow-up review by the onshore lead as needed.
Launch
The review cycle continues until all views meet MSFT SM standards. Once approved, the page is queued for go-live. Further changes after launch are fast-tracked.
Transitioning into the role of Design Lead from Sr. Designer, I currently lead one out of the three design pods handling various Microsoft products. With a 3-member team at my disposal, my pod is responsible for the page designs & QAs of key products like M365, Copilot, Teams, Viva & Events. Some of my key responsibilities involved:
Initiatives
I actively identified production and design gaps, built accelerator tools, and created design guidelines to improve speed, consistency, and efficiency. From conceptualizing new ideas to establishing smoother workflows and scalable processes, my initiatives helped teams work faster, smarter, and more collaboratively.

Copilot Guidelines
To support Copilot design revamp, initiated theming guidelines to standardise designs and reduce errors.

Designer Onboarding
Quick step-by-step guide to understand the flow of work in a pod. Designed for newly onboarded designers.

HO Fastrack
Implemented a faster, more accurate handoff process for production, making the process ~20% faster.

Content checklist
Drafted 14 checkpoints to minimise copy error within the team and increase overall output accuracy.

Team Retrospective
Initiated internal feedback loop to proactively identify gaps and opportunities in the team.

ACOM Page Designs
We ideated new ACOM page designs and used Adobe Firefly to create stunning visuals.


One of the key billable accounts, this project required deep understanding of UI/UX design and a thorough operational mindset.
400+
page designs
250+
design QAs
17
members
We’re here!

Give the requirement to the onshore team, and are responsible for the final approval on the designs before the pages go-live.
Based in Seattle, USA, collaborate directly with the SMs, gather the requirement & streamline the design process.
Based in Bengaluru, India, create pages as per requirement, and collaborate with the offshore team.
With teams based in both locations, collaborate with both Onshore/Offshore design teams to launch the pages after strict QA process.
Despite geographical distribution, clear communication maintains clarity, speed, and accountability. Two-way loops ensure seamless flow of ideas and feedback between teams, enabling rapid iteration and a unified vision.

And I’m here,
with my team!

Process Flow
Page Designing
Requirement gathering
Onshore team/leads gets feedback/requirement from MSFT and the shares them via Workfront.
Design
Offshore leads assign it to respective designers. Designers work on the tickets in accordance with MSFT design guidelines & themes.
Design Review
Offshore lead reviews the work, suggesting changes as needed. The Content team conducts a detailed copy review. Review rounds continue with stakeholders until the final design is achieved.
Handoff
Post review all related assets are shared as HO folders to dev team for production. Post-production, the designs are sent for QA.
Quality Assessment
Ticket Allocation
Dev team segregates Design QA tickets by pod and product, creates them in Workfront, and assigns to the offshore lead for delegation.
QA Review
Designers compare preview pages with Figma to find issues. Each bug is documented with descriptions and screenshots linked to the parent ticket.
Issue Resolution
Authors address the reported bugs. Designers close the ticket once issues are resolved, triggering a final review by the offshore lead and a follow-up review by the onshore lead as needed.
Launch
The review cycle continues until all views meet MSFT SM standards. Once approved, the page is queued for go-live. Further changes after launch are fast-tracked.
Transitioning into the role of Design Lead from Sr. Designer, I currently lead one out of the three design pods handling various Microsoft products. With a 3-member team at my disposal, my pod is responsible for the page designs & QAs of key products like M365, Copilot, Teams, Viva & Events. Some of my key responsibilities involved:
Initiatives
I actively identified production and design gaps, built accelerator tools, and created design guidelines to improve speed, consistency, and efficiency. From conceptualizing new ideas to establishing smoother workflows and scalable processes, my initiatives helped teams work faster, smarter, and more collaboratively.

Copilot Guidelines
To support Copilot design revamp, initiated theming guidelines to standardise designs and reduce errors.

Designer Onboarding
Quick step-by-step guide to understand the flow of work in a pod. Designed for newly onboarded designers.

HO Fastrack
Implemented a faster, more accurate handoff process for production, making the process ~20% faster.

Content checklist
Drafted 14 checkpoints to minimise copy error within the team and increase overall output accuracy.

Team Retrospective
Initiated internal feedback loop to proactively identify gaps and opportunities in the team.

ACOM Page Designs
We ideated new ACOM page designs and used Adobe Firefly to create stunning visuals.


One of the key billable accounts, this project required deep understanding of UI/UX design and a thorough operational mindset.
400+
page designs
250+
design QAs
17
members
We’re here!

Give the requirement to the onshore team, and are responsible for the final approval on the designs before the pages go-live.
Based in Seattle, USA, collaborate directly with the SMs, gather the requirement & streamline the design process.
Based in Bengaluru, India, create pages as per requirement, and collaborate with the offshore team.
With teams based in both locations, collaborate with both Onshore/Offshore design teams to launch the pages after strict QA process.
Despite geographical distribution, clear communication maintains clarity, speed, and accountability. Two-way loops ensure seamless flow of ideas and feedback between teams, enabling rapid iteration and a unified vision.

And I’m here,
with my team!

Process Flow
Page Designing
Requirement gathering
Onshore team/leads gets feedback/requirement from MSFT and the shares them via Workfront.
Design
Offshore leads assign it to respective designers. Designers work on the tickets in accordance with MSFT design guidelines & themes.
Design Review
Offshore lead reviews the work, suggesting changes as needed. The Content team conducts a detailed copy review. Review rounds continue with stakeholders until the final design is achieved.
Handoff
Post review all related assets are shared as HO folders to dev team for production. Post-production, the designs are sent for QA.
Quality Assessment
Ticket Allocation
Dev team segregates Design QA tickets by pod and product, creates them in Workfront, and assigns to the offshore lead for delegation.
QA Review
Designers compare preview pages with Figma to find issues. Each bug is documented with descriptions and screenshots linked to the parent ticket.
Issue Resolution
Authors address the reported bugs. Designers close the ticket once issues are resolved, triggering a final review by the offshore lead and a follow-up review by the onshore lead as needed.
Launch
The review cycle continues until all views meet MSFT SM standards. Once approved, the page is queued for go-live. Further changes after launch are fast-tracked.
Transitioning into the role of Design Lead from Sr. Designer, I currently lead one out of the three design pods handling various Microsoft products. With a 3-member team at my disposal, my pod is responsible for the page designs & QAs of key products like M365, Copilot, Teams, Viva & Events. Some of my key responsibilities involved:
Initiatives
I actively identified production and design gaps, built accelerator tools, and created design guidelines to improve speed, consistency, and efficiency. From conceptualizing new ideas to establishing smoother workflows and scalable processes, my initiatives helped teams work faster, smarter, and more collaboratively.

Copilot Guidelines
To support Copilot design revamp, initiated theming guidelines to standardise designs and reduce errors.

Designer Onboarding
Quick step-by-step guide to understand the flow of work in a pod. Designed for newly onboarded designers.

HO Fastrack
Implemented a faster, more accurate handoff process for production, making the process ~20% faster.

Content checklist
Drafted 14 checkpoints to minimise copy error within the team and increase overall output accuracy.

Team Retrospective
Initiated internal feedback loop to proactively identify gaps and opportunities in the team.

ACOM Page Designs
We ideated new ACOM page designs and used Adobe Firefly to create stunning visuals.


One of the key billable accounts, this project required deep understanding of UI/UX design and a thorough operational mindset.
400+
page designs
250+
design QAs
17
members
We’re here!

Give the requirement to the onshore team, and are responsible for the final approval on the designs before the pages go-live.
Based in Seattle, USA, collaborate directly with the SMs, gather the requirement & streamline the design process.
Based in Bengaluru, India, create pages as per requirement, and collaborate with the offshore team.
With teams based in both locations, collaborate with both Onshore/Offshore design teams to launch the pages after strict QA process.
Despite geographical distribution, clear communication maintains clarity, speed, and accountability. Two-way loops ensure seamless flow of ideas and feedback between teams, enabling rapid iteration and a unified vision.

And I’m here,
with my team!

Process Flow
Page Designing
Requirement gathering
Onshore team/leads gets feedback/requirement from MSFT and the shares them via Workfront.
Design
Offshore leads assign it to respective designers. Designers work on the tickets in accordance with MSFT design guidelines & themes.
Design Review
Offshore lead reviews the work, suggesting changes as needed. The Content team conducts a detailed copy review. Review rounds continue with stakeholders until the final design is achieved.
Handoff
Post review all related assets are shared as HO folders to dev team for production. Post-production, the designs are sent for QA.
Quality Assessment
Ticket Allocation
Dev team segregates Design QA tickets by pod and product, creates them in Workfront, and assigns to the offshore lead for delegation.
QA Review
Designers compare preview pages with Figma to find issues. Each bug is documented with descriptions and screenshots linked to the parent ticket.
Issue Resolution
Authors address the reported bugs. Designers close the ticket once issues are resolved, triggering a final review by the offshore lead and a follow-up review by the onshore lead as needed.
Launch
The review cycle continues until all views meet MSFT SM standards. Once approved, the page is queued for go-live. Further changes after launch are fast-tracked.
Transitioning into the role of Design Lead from Sr. Designer, I currently lead one out of the three design pods handling various Microsoft products. With a 3-member team at my disposal, my pod is responsible for the page designs & QAs of key products like M365, Copilot, Teams, Viva & Events. Some of my key responsibilities involved:
Initiatives
I actively identified production and design gaps, built accelerator tools, and created design guidelines to improve speed, consistency, and efficiency. From conceptualizing new ideas to establishing smoother workflows and scalable processes, my initiatives helped teams work faster, smarter, and more collaboratively.

Copilot Guidelines
To support Copilot design revamp, initiated theming guidelines to standardise designs and reduce errors.

Designer Onboarding
Quick step-by-step guide to understand the flow of work in a pod. Designed for newly onboarded designers.

HO Fastrack
Implemented a faster, more accurate handoff process for production, making the process ~20% faster.

Content checklist
Drafted 14 checkpoints to minimise copy error within the team and increase overall output accuracy.

Team Retrospective
Initiated internal feedback loop to proactively identify gaps and opportunities in the team.

ACOM Page Designs
We ideated new ACOM page designs and used Adobe Firefly to create stunning visuals.
