Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Posted by Ken Barlow
Ken Barlow
16,177 Points

Changes in design along the development process.

Just want to say Sarah Parmenter I really enjoyed the course you taught on Mobile App Design for iOS. I've learned a lot and am already putting it to use. :)

However, I do have a question and that's: What would you say the process should be for when a client continues to make significant changes to the design throughout the development process? How would you suggest this be handled?

2 Answers

Sarah Parmenter
STAFF
Sarah Parmenter
Treehouse Guest Teacher
Sarah Parmenter
Sarah Parmenter
Treehouse Guest Teacher

Hi Ken,

Thanks for your question. The way I handle this is to put a clause in my contract that states the client is paying for my time and not the finished product. I also state that hours will be handled via time tracking software that they can log into and view at any point. That way, they don't feel restricted with the changes, but are aware that when they make changes, the clock is ticking.

I always send them an email when we're down to 6 hours in the bank, asking them how they would like them to be used, remind them that they can continue to make changes but once our hours are up, they'll either have to add more or have the project handed over as is.

I've always found this a better way of working. If you restrict it to "certain number of revisions" it's always dubious as to what constitutes a revision. A page of 100 changes or 3 changes? It's too ambiguous .

Another tip - when they do send changes across, pop them back an email saying how long, in your professional opinion, it will take to complete that set of changes.

I think it's just about communication and transparency.

Hope that helps!

Patrick Cooney
Patrick Cooney
12,216 Points

Very fair point about set numbers of revisions. I'm glad you pointed that out. I'll have to change my wording.

Patrick Cooney
Patrick Cooney
12,216 Points
Patrick Cooney
Patrick Cooney
12,216 Points

So, this wont help now but may on the next go around... A suggestion I have from print experience: treat every project as if the client is going to ask for significant and numerous changes. You should write into the contract the scope, time frame and number of changes that are allowed without the client incurring extra fees. If they make changes after that date or outside the scope of what's allowed or ask for changes beyond the number of agreed upon revisions you should bill them separate hours for those changes.