I Gotta Learn How to Say No
I'm not sure how or why it started, though I have a clue.
Seems I've been branded a web developer, but that's not what I do.
It takes me twice as long to code, learning as I go
I'll be outsourcing this stuff from now on, but prices will grow.
I'm a Conversation Conductor, it says so to the right
I build communities of customers, if I'm not coding all night.
My fault, really - I get excited when a company says YES
They want to start a blog, so I do whatever it takes I guess.
But this model isn't working, no coaching is getting done
I'm as guilty as others, sending them into battle with a loaded gun.
Companies are moaning that their month old blog has no success
Why? They wrote one post last week (same text as their brochure, no less).
Suggest they read other blogs, even make a comment or three.
They don't have time. Reading other blogs waste their time, you see.
They want to ride on this bandwagon, "Please build us a blog site."
Folks the tool is not the answer, the conversation is what gives it flight.
Six Five code-heavy projects still on the table, but after that no more
Want to build a community of customers? You've come to the right door.
Comments