Question of deliverables and other such stuff
•Télécharger en tant que PPTX, PDF•
3 j'aime•2,677 vues
Slides from the talk I gave at Responsive Day Out 2 - The Squishening, June 27th 2014
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
Similaire à Question of deliverables and other such stuff
Similaire à Question of deliverables and other such stuff (20)
Plus de Kirsty Burgoine
Plus de Kirsty Burgoine (9)
Dernier
Dernier (20)
Question of deliverables and other such stuff
- 1. https://flic.kr/p/e2Kp5x A question of deliverables and other such stuff Kirsty Burgoine - @kirstyburgoine
- 8. Discuss Plan Design Build Job Done! Project Workflow in “Olden” Days
- 9. 2010 - Freelance Olden Days
- 10. https://flic.kr/p/8XqJLK - with added cats by ME
- 15. disclaimer...
- 16. Disaster Parakeet is the ultimate Badass…. ~ grin!
- 18. 1. Tell Them Nothing!
- 19. SURPRISE!!!
- 20. Clients were very happy Didn’t need to change my workflow at all Advantages of this approach:
- 21. No planning for mobiles / steep learning curve for me :( Additional time / costs Dis-advantages of this approach:
- 22. 2012 Approach 2 2013 2014 The Future…
- 25. Client still kn I could plan wClients were happy - they still knew what to expect for desktop Didn’t need to change my workflow much Could increase timescales and costs Advantages of this approach:
- 26. Dis-advantages of this approach: The client had no idea what to expect the mobile version to look like or any understanding of how it would work.
- 27. Approach 3 2012 2014 The Future… 2013
- 28. 3. Straight to the Code!
- 29. Drastic action
- 30. New Project Workflow... + Discuss Build Plan Job Done! Discuss
- 34. Actual Comments “I’m concerned about the number of straight lines, could you use this blue map marker instead?”
- 35. Actual Comments “I’ve sent you some designs I think would work but I don’t have Photoshop so I’ve done them in Excel”
- 36. Able to get the data in at a very early stage Advantages of this approach:
- 37. Dis-advantages of this approach: No deliverables so the client didn't trust what I was doing
- 40. A More Practical Approach.
- 41. My Current Project Workflow Discuss Plan Job Done!Design Build Plan Design Design Build Discuss Discuss
- 42. https://flic.kr/p/bBqABo I show them my ideas...
- 43. Lessons learnt Trust between you and the client is even more important now. It needs to be nurtured.
- 44. Lessons learnt Plan and budget properly for the time needed - Surprises are never a good idea.
- 45. Lessons learnt Set expectations for all aspects of the project from the beginning.
- 46. Lessons learnt Don’t leave the client to their own devices.
- 47. Lessons learnt If you can’t provide clearly defined deliverables, still show them your ideas. Don’t leave the client to their own devices.
- 48. Lessons learnt… a more personal one Make less gigantic decisions or at least plan them better!
- 49. Kirsty Burgoine @kirstyburgoine Icons and robot dude by @stina_jones Thanks.
Notes de l'éditeur
- Who am I - Jeremy invited me - shit - what could I bring to the table…
- my experience - unique to me - explain mistakes - more interesting And if not, I do have some animated gifs to keep you entertained
- ask everyone to stand up
- Would you perform this exercise with the person next to you?
- Trust needs to be nurtured, it doesn’t just magically appear
- one way to grow trust is to provide deliverables at key stages of the project
- time travelling - when your project workflow looked something like this…
- Theres not much work in building trust in this setup,
- More time travelling - I naively thought it would be something like this…
- A utopia of learning and cats and time… and obviously that is me in my pink house! But that wasn’t the case
- Jump forward 2 years
- A huge decision
- I considered myself late to the party. But that raised a lot of new questions
- How do I approach my workflow? What deliverables do I provide to the client to maintain that level of trust?
- From the point of view the client this was my favourite approach
- grand unveil. Show them the website I promised and then ask them to resize their browser window
- this kinda worked-ish. But...
- Because I had told them nothing. So I made the decision that neither of these were good options so I would try this “Designing in the browser” malarkey....
- This was radical! Basically scrap everything I’d done before and design in the browser...
- We’d discuss things, I’d scribble things down as ideas and then straight into the build. The idea was simple, build actual wireframes, starting incorporating the data and allow the design to grow around it. Job done! But...
- Who remembers this? I love this and still laugh at it. My favourite parts were the client comments and especially this one..
- Although it became less funny when I received this...
- Now, if I was to try to boil my workflow down into one definable way of working it would kind of look like this. Because I can’t