“Can we just quickly change that primary key?” ๐Ÿ˜ฑ

“Can we just quickly change that primary key?” ๐Ÿ˜ฑ

“Could you add this field real quick?” ๐Ÿคจ

“Hey, I caught you in the hallway…” ๐Ÿ˜…

These are some dangerous phrases that could spell trouble if you’re a consultant working on a staff augmentation model with a client!

Here are some critical tips I shared in my video about working as a staff aug consultant:

๐Ÿฉ Know your SOW (Statement of Work)! Is it a deliverable-based or activity-based engagement? This defines your scope and obligations.

๐Ÿฉ Document EVERYTHING in your timesheets

Not just “8 hours – functional build”

Break it down: What user stories? What meetings? What rework?

Record those “small requests” that add up

๐Ÿฉ The Hallway Request Trap When you get those “quick requests”, always:

– Follow up with an email to document

– Confirm understanding

– Check impact before implementing

– Get sign-off

I’ve seen too many projects go sideways because of undocumented “small changes” and unclear expectations. ๐Ÿ˜ฃ

What’s your experience with staff augmentation projects?

Any horror stories to share?

#OnThePeiroll

ps: This was my first impromptu LinkedIn Live! If you found it useful, let me know and I’ll do more of these quick knowledge-sharing sessions! ๐Ÿ˜Š