Transparency Between Developers and Clients
0 likes197 views
The document discusses the importance of client transparency throughout the creative development process, highlighting lessons learned from real-life client interactions and project management challenges. It emphasizes the need for clear communication, realistic cost expectations, and the establishment of well-defined contracts to prevent misunderstandings and scope creep. The author shares insights from case studies that underline the significance of pre-qualifying projects and maintaining open dialogue for successful partnerships.
Transparency Between Developers and Clients
- 1. Client Transparency In Creative Development D E S I G N T H E O R Y
- 2. What Will You Learn? In this talk I will discuss the necessity of honesty with clients from the discovery phase all the way post launch follow ups. I’ll also reveal some real life scenarios I’ve experienced in dealing with some difficult client projects and situations. D E S I G N T H E O R Y
- 3. How You Imagine Us Typical Day/Life Assumptions: • Drinking the best caffeinated lattes baristas have to offer • Coding is a piece of cake • Playing video games all day • Learning through Osmosis • Spending hours online reading blogs • On all social media and other corners of the Interwebs D E S I G N T H E O R Y
- 4. Start Finish 9pm 3am In Reality We are actually reading industry news, checking social media, and making ourselves more valuable in the marketplace. D E S I G N T H E O R Y
- 5. How We Imagine You D E S I G N T H E O R Y
- 6. Some Basic Hesitations With Transparency • The true cost of development time • Intellectual property (IP) is invaluable • The hours of the day/night we’re working • We’re working on multiple projects at once • Your project needs to be interesting • Our rates are subject to change based on your attitude • This next project may be exactly what I need to clear an upcoming bill or necessity D E S I G N T H E O R Y
- 7. Had no research or proof of concept or viability other than word of mouth. Paid advertising was also out of the question. Had an project budget of under $2,000 yet had the expectation for a service level of 50-60k. Wanted to compete with already existing and well known brands like Expedia and Travelocity. CASE STUDY: The Travel Company D E S I G N T H E O R Y
- 8. What Did I Learn? • It should never be about the money first • I should have pre-qualified the project AND client • Better explained to the client a more realistic cost that would make for a successful business website • Since I didn’t have any real industry knowledge, I may have costed myself hours of research during the project that wasn’t going to be billable. • Understood my target client profile D E S I G N T H E O R Y
- 9. There’s a greater chance of scope creep with so many chef’s in the kitchen. Was used as a scapegoat for missed deadlines or additional fees. GC’s will sometimes add things that were never discussed previously. Contracts can be crucial in protecting a developer especially if someone drops out of the project Three different interpretations of what the ideal website should be. Took weeks to get into agreement for the little things, while the bigger concepts were ignored. CASE STUDY: Third Party Developer D E S I G N T H E O R Y
- 10. What Did I Learn? • Have a bullet-proof contract specifically for TP projects • Not be afraid to enforce the contract when necessary • Request all necessary content and materials be turned in before the commencement of the project • Create sign-off points from the TP throughout the course of the project that will help prevent scope creep • Admitted any shortcomings to the TP that I may have fulfilling this project in my capacity. D E S I G N T H E O R Y
- 11. #01 I have real feelings, and real emotions, and start out really positive about each project. #02 #03 #04 What Should You Do & What You Should Know It’s in both our best interests to have an agreed upon contract. No matter how many pages it is in length. Not responding to emails or phone calls, or dragging your feel on requirements can extremely hinder your project. #05 Your honest feedback is appreciated, but needs to be substantiated with good reasoning. If you admit you’ve had several problems with previous developers in the past, it’s an honest red flag for me. D E S I G N T H E O R Y
- 12. Design Theory HQ Orlando, FL 32824 C O N T A C T U S T +407.490.2425 @jpDesignTheory (everywhere) URL www.jpDesignTheory.com MAIL email@jpDesignTheory.com It’s easy to get in touch with us