Time when you motivated a team during a challenging project?
Situation
- Billing service from scratch
- Payment gateway failures under load
- Tight deadline, team morale low
Task
- Keep team motivated
- Solve technical bottlenecks
- Deliver on time
Action
- War-room huddles → big picture + small chunks
- Pair programming for tricky parts
- Adjusted priorities, pushed back non-critical
- Transparent with stakeholders
- Celebrated small wins daily
Result
- Service stable → 3x load capacity
- Launched on time
- Positive leadership feedback
- Team more confident & resilient
Situation:
At SaaS Labs, my team was building a new billing and balance service from scratch. Midway, we hit a major roadblock: integration with multiple payment gateways was failing under high load, and deadlines were tight because the launch was tied to a client commitment. The team was frustrated and morale dipped.
Task:
As the engineering manager, I had to keep the team motivated, ensure focus on solving the technical bottlenecks, and deliver the service on time without burning out the team.
Action:
- I first organized a short war-room style huddle to acknowledge the challenge, remind the team of the bigger picture, and divide the problem into smaller solvable chunks (e.g., retry mechanism, idempotency handling, performance tuning).
- I encouraged a pair-programming approach for the trickiest parts, so no one felt stuck alone.
- To reduce stress, I adjusted priorities, pushed back on a few non-critical features, and communicated transparently with stakeholders.
- I also celebrated small wins daily (e.g., “retry logic stabilized at 5K RPS today”) to keep spirits up.
Result:
The team regained momentum and, within two weeks, we stabilized the billing service to handle 3x the expected transaction load. We launched on time, received positive feedback from leadership, and the experience strengthened team confidence in handling high-pressure situations.