Comments on: The value of business knowledge http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html Tech' views that are 667% more interesting than the tech' news itself... Wed, 03 Dec 2008 05:52:59 +0000 http://wordpress.org/?v=2.6 By: Wayne Smallman http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-1003 Wayne Smallman Sat, 03 Nov 2007 11:01:43 +0000 http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-1003 Guys, you've all managed to uncover some very, very interesting and thought-provoking points. And thanks Jerad, I can relate to a lot of what you say. I was there myself, during those early days. I remember the feeling of being a magician all too well. I might need to follow this article up at some point... Guys, you’ve all managed to uncover some very, very interesting and thought-provoking points.

And thanks Jerad, I can relate to a lot of what you say. I was there myself, during those early days. I remember the feeling of being a magician all too well.

I might need to follow this article up at some point…

]]> By: Jerad Kaliher http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-1001 Jerad Kaliher Sat, 03 Nov 2007 06:50:40 +0000 http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-1001 Back in 1996 I was a web designer and at the time there was, quite literally, no basis for comparison. The entire process of development, marketing and strategy were immaterial "old world" concepts that couldn't apply to such a radically new medium. Learning as you went was essential because the people that contracted you literally believed that simply creating a website was enough to drive business. The client expectations then were minimal because the general idea was that websites, "took a while to catch on." Consulting as a designer took on the tone of inventor rather than partner. It was magic, one day it wasn't there the next it was. As long as there was simple functionality you survived the first paycheck. It was driving traffic, staying away from faulty coding styles and continuous evolution that defined the next generation of developers. The difference now is that clients are able to compare past data and make assumptions on the future of their investment. The role of inventor is no longer welcome unless a strong relationship is forged and part of the plan is to push the boundaries of the genre. Now, the successful modern developer paints the picture the client desires and needs strong communication to portray the changes that may deviate from the original plan. Back in 1996 I was a web designer and at the time there was, quite literally, no basis for comparison. The entire process of development, marketing and strategy were immaterial “old world” concepts that couldn’t apply to such a radically new medium.

Learning as you went was essential because the people that contracted you literally believed that simply creating a website was enough to drive business. The client expectations then were minimal because the general idea was that websites, “took a while to catch on.”

Consulting as a designer took on the tone of inventor rather than partner. It was magic, one day it wasn’t there the next it was. As long as there was simple functionality you survived the first paycheck. It was driving traffic, staying away from faulty coding styles and continuous evolution that defined the next generation of developers.

The difference now is that clients are able to compare past data and make assumptions on the future of their investment. The role of inventor is no longer welcome unless a strong relationship is forged and part of the plan is to push the boundaries of the genre.

Now, the successful modern developer paints the picture the client desires and needs strong communication to portray the changes that may deviate from the original plan.

]]> By: Heidi Cool http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-971 Heidi Cool Thu, 01 Nov 2007 16:41:03 +0000 http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-971 Wayne, I think education is key. I'm actually meeting with a fellow this afternoon who wants to learn how he can maintain his site. Last week I taught him blogging, but I think he'll quickly grasp how much more complicated this is, then grant it due respect. (He's an amiable and bright fellow.) In terms of learning on the job, in a field that is ever-changing I don't see how we can get around it. The best way to learn is with real projects. But in the long run everyone benefits. When working for client B, you may be applying skills that you learned on a project for client A. What you learn with B can be applied to C and so on. Now in three years when B wants a new site, you'll be coming in with a whole new slew of skills. And then begin to learn some more... Wayne,
I think education is key. I’m actually meeting with a fellow this afternoon who wants to learn how he can maintain his site. Last week I taught him blogging, but I think he’ll quickly grasp how much more complicated this is, then grant it due respect. (He’s an amiable and bright fellow.)

In terms of learning on the job, in a field that is ever-changing I don’t see how we can get around it. The best way to learn is with real projects. But in the long run everyone benefits. When working for client B, you may be applying skills that you learned on a project for client A. What you learn with B can be applied to C and so on. Now in three years when B wants a new site, you’ll be coming in with a whole new slew of skills. And then begin to learn some more…

]]> By: Wayne Smallman http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-948 Wayne Smallman Wed, 31 Oct 2007 17:15:06 +0000 http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-948 Hi Kristina and thanks for taking the time out to comment. You'd be surprised at how many businesses say "Yes!" to everything the client asks for and then worry about the execution afterwards. I'm not afraid to say "No", but I always give valid reasons. Sometimes, saying no can close doors and instigate some element of internal political pressure. But if you're sure of your point, don't be afraid of the power of no.. The best way to educate a client is to talk them through their ideas and investigate the various scenarios. Doing this usually uncovers the problems you'd no doubt encounter along the way, avoiding costly wasted effort... Hi Kristina and thanks for taking the time out to comment.

You’d be surprised at how many businesses say “Yes!” to everything the client asks for and then worry about the execution afterwards.

I’m not afraid to say “No”, but I always give valid reasons. Sometimes, saying no can close doors and instigate some element of internal political pressure. But if you’re sure of your point, don’t be afraid of the power of no..

The best way to educate a client is to talk them through their ideas and investigate the various scenarios.

Doing this usually uncovers the problems you’d no doubt encounter along the way, avoiding costly wasted effort…

]]> By: Kristina Sontag http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-947 Kristina Sontag Wed, 31 Oct 2007 16:50:08 +0000 http://www.blahblahtech.com/2007/10/the-value-of-business-knowledge.html#comment-947 This is a fantastic point, especially for clients who want something that stands out or pushes the envelope. I believe often we need to spend more time educating our clients on what it is we do for them, and why it does take so long to make "simple" changes sometimes. This of course leads into a conversation about how to make sure the client has thought through their needs BEFORE a line of code goes down to minimize those sorts of changes, and if anyone has tips on that I'd love to hear them! This is a fantastic point, especially for clients who want something that stands out or pushes the envelope. I believe often we need to spend more time educating our clients on what it is we do for them, and why it does take so long to make “simple” changes sometimes. This of course leads into a conversation about how to make sure the client has thought through their needs BEFORE a line of code goes down to minimize those sorts of changes, and if anyone has tips on that I’d love to hear them!

]]>