[Sigia-l] Re: Where's the reality?

[Donna Maurer]

I wonder whether this has less to do with 37 Signals approach and more to do with the 
fact that this type of deliverable-based consulting does not suit the type of IA work we 
do.

I gave up consulting because I hated the consultancy approach - estimate how many 
days it will take to make a 'sitemap' and a set of 'wireframes' based on a set of pre-
defined 'activities', while knowing that I was committing myself to sub-standard work 
by doing so. I knew full well that I needed some time to soak up the context and do 
some of the research before I knew how hard the job was going to be.

Now I only take jobs where I have the freedom to explore and, after exploring, create 
*good* work. I don't commit to a delivery date for a deliverable, but commit to a good 
outcome within a period of time. This is different in practice to the 37 Signals 
approach, but similar in concept. And it works. But it doesn't necessarily suit rigid 
project management approaches that require certain documents on certain dates. It 
doesn't suit anyone who can't cope with me saying 'this bit here, this is thinking time'. 

I think there is loads of interesting stuff in their approach that can benefit all my 
projects. As with any 'method' it suits some projects better than others and some 
teams better than others. 

But the underlying principles are good. In the end, every client wants a good product. 
That's what's important.

And I have no hesitation in saying that I've been drinking the 37 signals kool aid since 
the release of basecamp. so there ;)

Donna

On 11 Mar 2006 at 19:14, Leisa Reichelt wrote:

> i guess it depends on the nature of the consultant relationship.
> Basically I'm concerned that the very short and non-specific 'scoping'
> phase advocated by the Getting Real methodology is potentially
> troublesome in a project where you and your 'client' have to agree on
> what the project is and the points at which you can agree that the
> work has been completed.
> 
> Given that functional specifications are a no-no in Getting Real and
> 'wireframes' are essentially rough sketches on paper that are coded
> ASAP, then move into an iterative release cycle, based on my
> experience I'd say that there would be a lot of arguing over whether
> or not a 'deliverable' had absolutely been achieved (meaning that your
> client then owes you money).
> 
> In the 37 Signals environment, this simply isn't an issue they need to
> deal with, so its relatively easy for them to ditch documentation like
> signed off wireframes and functional specifications. Where there's
> ongoing client expectation management required - documentation can be
> very helpful!
> 
> Would be interested to hear others thoughts on this :)
> 
-- 
Donna Maurer
Maadmob Interaction Design

e: donna at maadmob.net
work: 	http://maadmob.com.au/
blog: 	http://maadmob.net/donna/blog/
AOL IM: maadmob