We'll be honest, it's a Friday arvo and we're looking for something light on the old noggin after a heavy week.
To keep the good times (and wines) flowing we decided to put together a light hearted read that is sure to evoke a few laughs. Without further ado — AM PM presents: the 13 stages of your digital design and dev web project, as brought to you by Twitter, memes and gifs.
This is a shamelessly shallow article and we're all for it!
#1 The brief: Understanding what the client wants
Welcome to your new project. We're still in the sales phase waiting for the client to consolidate their brief. This is the time those classic contradictions come to light — like "Can you add x, y and z to the project scope? But also we can't afford $50k, so can you go easy on us?"
#2 Kickoff: Putting your plans in place
Alright so you settled on $40k and are finally pumped to kick start this new project.
The client keeps referring to an agile approach...yet also needs everything delivered in a linear format with strict deadlines and scope.
#3 Scope approval: Getting sign off on that pesky SoW
Yep it's the fun part. Reading those T&Cs and long winded SoW documents. Agreeing on the complete scope can be like getting blood from a stone as you chase the client round in circles.
#4 Design: Getting your designer knee-deep in the work
Finally time to get cracking in design. You're gifted a shitty logo and a brand guide circa 1990, but the client needs the site to be 'sophisticated' and 'contemporary'.
#5 Internal QA: Reviewing your designer's work prior to client handover
Yeahhhhh so you have 20 QA items....and your designer has skipped about 13.5 of those. Wot?
#5(b) Internal QA: Your designers take on your QA ideas
Okay round two of your internal QA. Maybe if you explain your feedback they'll actually do it this time?
#6 Design handover: The calm before the storm when first handing over designs
The moment of truth. Design handover is where things sink or swim. They say 'no news is good news' but it doesn't feel that way with designs. Just sit back and pray it goes smoothly.
#7 Design feedback: Getting super positive feedback from the client (woohoo)
Alright things are looking good. Thumbs up from the client on those design concepts. We're headed in the right direction (AKA under budget and timely delivery).
#7(b) Design feedback 2.0: Spoke too soon, your client starts to trickle through feedback
Anddd the client changes their mind. They didn't actually consolidate feedback until now and the rest of their (non-designer) team have some specific ideas on how to "jazz up" the designs because they just don't "feel right".
#7(c) Design feedback 3.0: Explaining why the client's design ideas are wrong and you're always right
So how do you put this delicately? Their ideas are crap and they're not UX/UI designers. So you will politely take on board their feedback and convert it from turd to polished turd with a cherry on top.
#7(d) Design feedback 4.0: Getting that after hours call
Oh sorry, you thought design revisions were done? Nope, they had a bit more to go. Chris from the IT department thought of a great new idea and the perfect time to discuss it is after hours.
#8 Development QA: A lotta visual & functional testing
This is where you truly understand how different your brain is from developers. The approved designs and staging site are fraternal twins...but you promised the client paternal twins. Time to start peppering your dev with visual improvements.
#8(b) Development QA: Your developers view of the QA feedback
Rough. But necessary.
#9 Client UAT: Chasing your clients on dev UAT...again
Just a friendly reminder that if you don't consolidate your UAT by Monday, we won't be able to make launch. So please don't expect the same delivery from us when you fail to meet your own deadlines.
#10 Actioning UAT: Finalising client UAT concerns
Disheartening. But necessary.
#11 Pre-launch: The countdown is on
You can taste the sweet, sweet taste of launch around the corner. Oh but wait, slightly more UAT feedback incoming.
#12 Launch day: You made it!
And only cried 6 times; complained to your desk neighbour 21 times; and punched your screen once.
#13 Celebrate: Sharing your project success on socials
Now time to celebrate your wins! The boss asks you to put together a social post on the work we achieved. Get the Linkedin peeps stroking our egos.
And hey presto, you're done.