1) POV

I joined ServiceNow India as the first designer for Core Business Workflows, hired into HR Service Delivery. As a Design Lead, I drove multiple high-stakes initiatives across HRSD, including Listening Posts, HR Integrations, Employee Journey Management, and HR Agent Workspace.

That execution, plus strong cross-functional trust, expanded my scope beyond delivery. I was asked to help establish and scale CBWF design teams in India. I directly built and managed teams across HRSD, Legal Service Delivery, and Contract Lifecycle Management, and supported adjacent teams through hiring, onboarding, and early mentoring.

2) Scale I drove

Before I get into how I did it, here’s the scale I was responsible for building and leading:

• HR Service Delivery (HRSD): 1 → 6 designers

• Legal Service Delivery (LSD): 1 → 2 designers

• Contract Lifecycle Management (CLM): 1 → 2 designers + 2 contractors

• 10 hires across pods

• 4 promotions supported across levels, including one move into people leadership

[ARTIFACT: Growth snapshot] Headcount timeline by pod, no names.

3) How it unfolded

When I joined, the India design footprint was still forming. I was delivering critical HRSD work while the IDC growth plan started materializing in parallel. As that plan became real, I started supported my Design Director on the first few hires, then gradually took full ownership of the team growth: hiring, onboarding, and shaping how design would operate across pods.

Team building here was not a single moment. It was a sequence of decisions made while the work was already moving.

Step 1: Seed the pods with the right first hires

In the early phase, the goal was not to add people. It was to place the first hires so pods could form across HRSD, LSD, and CLM with real ownership, not just execution coverage.

Some roles required a rare mix: enterprise execution plus enough strategic judgment to hold ambiguity with PM and Engineering. When I found high-slope candidates who were strong on most dimensions and rampable on a few, I hired with an explicit 6–12 month ramp plan and owned that investment.

[ARTIFACT: Hiring rubric] Anonymized scorecard.
[ARTIFACT: 30-60-90 onboarding] Ramp plan with “first win” examples.
[ARTIFACT: Kudos card] New-hire recognition for onboarding support.

Step 2: Make ownership visible so the org doesn’t route through one person

As the team formed, PMs and leaders would often ask in release cycles: “Who owns this from design?”

That question was a sign the org needed legible ownership as scope expanded. So I made pod ownership explicit across HRSD, LSD, and CLM, with clear partner touchpoints. The goal was to make design predictable for the org and to make ownership real for the team.

[ARTIFACT: Pod + ownership map] Pods, what they own, partner touchpoints.

Step 3: Build owners through scope, feedback, and sponsorship

Scaling teams is really about leadership density. I needed more people who could run rooms, drive tradeoffs, and protect quality without escalation.

I built that through three repeatable loops:

• Scope shaping: feature slice → workflow area → roadmap thread, over 2–3 cycles

• Early feedback: problem framing and tradeoffs first, UI later

• Sponsorship: pod owners presenting in key reviews once the narrative was ready

Promotions were a downstream result of readiness built through scope and coaching, not timing.

[ARTIFACT: Level expectations] Behavior-based ladder (no internal level codes).

Step 4: Keep the team sustainable as the surface area grows

Scaling also breaks in quiet ways: overload, meeting bloat, and “yes” becoming the default.

One designer struggled with saying no because they worried it would harm relationships. We practiced a different posture: “no” as a tradeoff and a path forward. Over time, boundaries strengthened trust and protected outcomes for everyone.

On the system side, I focused on meeting hygiene. We reduced recurring meetings, kept critique and working sessions as the only defaults, and protected focus for makers.

[ARTIFACT: “No, but…” patterns] Reusable pushback scripts.
[ARTIFACT: Kudos card] Team recognition for support and collaboration.

I also hired and developed intentionally to build balanced pods, not clones. Different strengths, different backgrounds, one shared bar.

4) Keeping standards coherent as the team grew

As pods scaled, I used lightweight critique to build shared judgment early and keep the bar consistent across the team. The proof for me is when critique changes direction, not when critique exists.

[ARTIFACT: Critique template] The format we used.
[ARTIFACT: Flow delta] Before/after of the manager hub and validation approach.

5) Where we landed

As the team settled in over the next 1–2 years, pods started running reviews directly with PM and Engineering, without me as the bridge. Partners came to pod owners first, and pods could run end-to-end discovery to delivery for their space. Strategic work increasingly became owned and driven from India, and co-located triads made execution smoother and more productive.

[ARTIFACT: Proof strip] Links to Listening Posts, Employee Journey Management, HR Agent Workspace.
[ARTIFACT: Kudos strip] New hire, team member, VP kudos (3 small cards, redacted).

Partner voice (redacted):
“Shivam has built a strong, high-performing HRSD and LSD design team in IDC. A lot of our strategic work is now owned and driven from India, and the co-located PM, Design, and Engineering triads have made execution smoother and more productive.”

Deeper dive:
[LINK] Building CBWF India design from 1 to X