Gluue » clients http://gluue.com Just another WordPress weblog Wed, 21 Dec 2016 14:23:49 +0000 en-US hourly 1 https://wordpress.org/?v=3.8.41 Feedback. When to Get it, When to Avoid it, and How Jumpchart Helps Keep Track of it All. http://gluue.com/2013/10/feedback-when-to-get-it-when-to-avoid-it-and-how-jumpchart-helps-keep-track-of-it-all/ http://gluue.com/2013/10/feedback-when-to-get-it-when-to-avoid-it-and-how-jumpchart-helps-keep-track-of-it-all/#comments Tue, 15 Oct 2013 13:54:48 +0000 http://gluue.com/?p=3131 If you’re using Jumpchart, you’re probably organizing content for a website project. And if you’re working on a website project, you probably know you’ll have to get feedback… at some point.

The hard part is deciding when. Early? Before you get into the nitty gritty? Or later? After you’ve already done the hard stuff? There are pluses and minuses to both. But because you’re using Jumpchart, you’re lucky… you can go either way and still stay on track. Here’s how.

Getting Feedback Early.


Picture this. You have big ideas for this site. You can’t wait to get started, but you’re working really closely with your client. Your idea of a partnership is a give and take – and that means feedback every step of the way. So you work through the architecture of the new site; that’s your step one. Maybe it goes something like this. Once you have that knocked out, it’s time to show your client. You have two options for letting your client see it. You can either invite them to the project (with full access, or read-only access – your choice!), or show them the public link to the site map. Inviting them to the project allows them to make comments on each page. Those comments will stay with you throughout the project’s existence, so you can always refer back to them to make sure you’re staying on the right track. You either get instant approval, or you and your client work through initial revisions together. Then you move on to the page-level content. Since you’ve already shown your client, they have access to your progress, and can provide feedback as you go. Your project progresses at a pace you’re both happy with, and as always, you can refer back to notes because they’re right there in your Jumpchart project.

Getting Feedback Later.


Or there’s the alternative – doing the bulk of the architecture work and content organization before getting feedback. Perhaps you (and your client!) prefer it this way, and that’s perfectly fine. Jumpchart is equipped to handle this workflow just as easily. Once you have all your i’s dotted and t’s crossed, show your client. You give them full access, and they make comments on each page. As you’re working through the edits, you have a linear path of what the client requested, and can visually show them when the work has been done. But it doesn’t end there. Because you gave your client full access when you invited them, they can make changes on their own – right there in the content section. You are always aware when changes are made because the recent events stream on the project homepage lets you know about any and all activity. But if they botch a bit of content by using grammar fit for a 4th grader, you can always go back in time by using the versioning feature. You can even choose to be emailed when a comment has been made, so you’re in the loop the whole time.

So, as you can see, whether you decide to get feedback out of the starting block, or halfway down the yellow brick road, Jumpchart helps make sure you do your job the best you can.

]]> http://gluue.com/2013/10/feedback-when-to-get-it-when-to-avoid-it-and-how-jumpchart-helps-keep-track-of-it-all/feed/ 27 Instant Gratification. http://gluue.com/2010/06/instant-gratification/ http://gluue.com/2010/06/instant-gratification/#comments Wed, 16 Jun 2010 14:59:43 +0000 http://gluue.com/?p=1859 How do you feel about instant gratification?

I enjoy it personally. It’s like waving a magic wand.

I’m spoiled by my programming co-workers. Sometimes I happen to stumble upon a bug, need an e-mail setting fixed on a server I don’t have access to, or have a question about the CMS we built from scratch; I can’t think of a single time when I’ve had to ask twice because I didn’t get an answer nearly immediately.

But throw clients into the mix, and you have an entirely different ballgame.It’s not unheard of these days for a programmer to also design, and the other way around. So therefore it’s not unheard of for a programmer to interact with clients. It might be as complex as explaining the inner workings of an app they’d like integrated into their site, or as simple as telling them their project is complete. It’s possible to provide instant gratification either way.

The term takes on a negative connotation as this outlandish request that can’t possibly be done- “Are they crazy? What do they expect, instant gratification?”

Well, yeah.

Give it to them once, and they expect it every single time. The bar is raised, expectations altered, and neediness increased. There’s a fine line between getting things done in a timely fashion, and getting them done too quickly. It’s a shame, though. You want to show your clients you can solve their problem in a matter of minutes, but you don’t wanna tell them how fast you are. If you do, they’ll ask for the moon, and let’s face it- you might not be able to give them the moon. Giving someone the moon is a HUGE job… and cannot be done quickly.

Dealing with clients who expect the world to revolve around them can be stressful, especially when you have 18 other projects on your plate. But, as sneaky as the solution sounds, don’t let it get to you. Barring a rush job that absolutely has to be done that second, don’t be afraid to put a little space between the moment the project is done, and when the client is notified that it’s done. It’ll still probably be quicker than they expected, anyway.

Giving and receiving instant gratification is definitely satisfying. Find the balance with your clients that lets you keep giving it, so they can believe they’re continuing to receive it.

]]> http://gluue.com/2010/06/instant-gratification/feed/ 0