[consulting] consulting Digest, Vol 62, Issue 20

Alex Urevick-Ackelsberg alex at zivtech.com
Wed Mar 23 20:53:16 UTC 2011


As someone who regularly crosses lots of people's boundaries, I'm probably
not the best one to talk, but I think you owe Kelly an apology. Asking "are
you stupid" is just a passive aggressive way of saying "you are stupid" and
that is not (IMO) an appropriate thing to say to someone on a list like
this...

--
Alex Urevick-Ackelsberg
Partner | CEO
Zivtech, LLC <http://zivtech.com>
alex at zivtech.com
office: (215) 922-2692
cell: (215) 866-8956
twitter: AlexU_A <http://twitter.com/alexu_a>



On Wed, Mar 23, 2011 at 4:49 PM, cliff ludriecus <ludo1960 at hotmail.co.uk>wrote:

>  ok that's a better anwer!
>
> ------------------------------
> From: tmw100 at me.com
> Date: Wed, 23 Mar 2011 13:46:19 -0700
>
> To: consulting at drupal.org
> Subject: Re: [consulting] consulting Digest, Vol 62, Issue 20
>
> I don't think it is "stupid". In fact, if you have had had the opportunity
> of working on a development project from the other side of the equation, you
> would probably have more insight.
> Yes, the whole team matters, but to the client - they could care less. The
> client want quality work and for that work to represent the vision and goals
> of the project. When things don't go that way, I seriously doubt any client
> has the time or disposition to consult every member of the team. They want
> one trusted point of contact, and they want that contact to be effective in
> seeing the goals met.
>
>
> On Mar 23, 2011, at 1:34 PM, cliff ludriecus wrote:
>
> "It's only ONE PERSON the client needs to trust - not the whole team"
>
> Are you stupid?
>
> > From: kelly at gothamcitydrupal.com
> > Date: Wed, 23 Mar 2011 15:34:17 -0400
> > To: consulting at drupal.org
> > Subject: Re: [consulting] consulting Digest, Vol 62, Issue 20
> >
> > > Nothing beats a collocated team when it comes to customer requirements
> analysis, rapid feedback, changes, and trust.
> >
> > I disagree. It's only ONE PERSON the client needs to trust - not the
> whole team. The implication being that the person the client needs to trust
> is the person responsible for their project, who assures the quality of the
> final work product. I'm addressing this (ironically, in this context) by
> having a distributed network of highly-skilled Drupal freelancers, all of
> whom run their own businesses and know how to handle client relationships.
> Because of the distributed nature of the team, there can be a local client
> in-peron relationship, if needed, because we're in all major markets (at
> least in the USA - I'm working on the global situation). I think it's
> incumbent on all of us to learn new ways to not have to work in the same
> room - for so many reasons I can't even keep count, among the most important
> of which is that many of the best people don;t want to work onsite - this
> confirmed by several Drupal recruiters I've asked about this. Because if one
> thing is clear to me, a dist
> > ributed workforce for coding is the future.
> >
> > > Some projects can be treated as commodities, but I believe the
> relationship between customer and consultant is vital to delivering the most
> useful and expected work items.
> >
> > Now THAT I completely agree with. Relationship and trust are everything.
> Otherwise you're drowning in a sea of paperwork, requirements documents, and
> all kinds of artificial "assurances" and CYAs that in the end, mean nothing
> outside a courtroom. And if you're in a courtroom, the relationship is
> certainly not going to be recoverable.
> >
> > Integrity and trustworthiness are the most important assets we have
> outside our technical knowledge, and they're the attributes that really set
> the best people apart. Those are the qualities my "partner evaluation
> rubric" (this algorithm I've made which factors a whole lot of qualities and
> skills and weights them, and is designed for Drupal coders specifically - my
> very own Certified to Rock) attached very high weighting to, with emphasis
> on previous direct working relationships.
> >
> > Kelly Bell
> > 917.446.1555
> > twitter: @kelly @gothamdrupal
> > LinkedIn: http://www.linkedin.com/company/gotham-city-drupal
> > http://gothamcitydrupal.com
> > http://drupal.org: kbell
> > freenode.irc: kbell
> > http://acquia.com/partners/showcase/gotham-city-drupal
> >
> > On Mar 23, 2011, at 2:51 PM, consulting-request at drupal.org wrote:
> >
> > > Nothing beats a collocated team when it comes to customer requirements
> analysis, rapid feedback, changes, and trust.
> > >
> > > Some projects can be treated as commodities, but I believe the
> relationship between customer and consultant is vital to delivering the most
> useful and expected work items.
> > >
> > > --Jim
> >
> > _______________________________________________
> > consulting mailing list
> > consulting at drupal.org
> > http://lists.drupal.org/mailman/listinfo/consulting
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
>
> _______________________________________________ consulting mailing list
> consulting at drupal.org http://lists.drupal.org/mailman/listinfo/consulting
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20110323/49cf7ff3/attachment-0001.html 


More information about the consulting mailing list