[Sigia-l] We could just use whiteboards instead.

[Derek R]

Marc wrote:

>| I'm sold on the way Big Stuff On The Walls changes
>| the conversation among the team, the way it leads to
>| new conversations, the way it helps immerse the team
>| in all the ideas


Again, I think, tho meaning well, Ziya is stuck in a fundamentalist rut,
in that dismissal of low-tech, common-denominator solutions in favor of
digital or otherwise high-tech formats is really just an indication of
being uncomfortable with contingent, transformative mediums (again the
skepticism of deconstruction) which empower autonomous, bottom-up
contributions. I think Ziya might not be able to bear to let someone
else assume control of a deliverable-in-the-making -- to let them engage
with it, so to speak -- and *make discovery available.* He might
consider himself a funnel through which all activity must go (ie.
design-by-dictatorship).

Furthermore, working within low-tech formats erases tendencies to flaunt
superior technological-knowledge, which may be disheartening to some.
This is to say the domination and influence gained by choosing a
difficult communication-medium is not particularly an issue with
white-board technology. Anybody can use a whiteboard; it's all-inclusive
and does not aim to talk-down to people or to solve the entire project
in one 'fully-functional' swoop.

In response to Ziya sitting alone with people in a room a la
Spanish-inquisition style, I do not believe this inspires loose and
candid thinking but more of a self-conscious, self-correcting,
formalized response. This is more like jamming pieces into a
pre-existing puzzle (wink wink, nod nod), whereas group spontaneity
affords real progress and discovery because that's where people's guards
are let down and information is more accurate and accessible.

I think also Ziya has confused those holding 'domain knowledge' with
their willingness to share it. He must have forgot the article he posted
recently on IT productivity which indicates people typically look-out
for #1. This means honesty and being-candid-about-things is not a core
attribute of self-reporting. You absolutely must create low-key
environments which promote interaction because therein lies
accomplishment (see <http://useit.com/alertbox/20010805.html>).

In fact, the greatest advantage low-fidelity flow-documents offer is
that they are NOT tangible, formal, declared things, so that (like many
have indicated), things remain on the conceptual-level, which is, of
course, the purpose of any early-stage design. I think formalized
highly-structured documents, even if just superficially so (ie. like
DENIM's digital representations of scratches-on-paper), is *too
white-collar* for what it intends to do -- in effect, systematizing the
brain-storming process -- an obvious oxymoron and obstacle to the stated
goal. Formalization promotes a tendency to fit pieces into a
pre-existing puzzle, which is contrary to accurate observation and
discovery.

When you stay outside of the constraints of a 'painting-by-the-numbers
philosophy' there is an obvious creative and innovation advantage which
increases the potential for *real breakthroughs.* Divorcing one's-self
from the same old tired formulas, to me, is the difference between doing
design and doing production-line work. If the stated business goals are
to dish-out neat-n-clean carbon-copy site maps and design-plans, (as
opposed to capably and genuinely engaging the content and business
model, an act of messy inclusion), then a formalized approach is likely
appropriate. However, status-quo production-line work is NOT appropriate
for businesses who value the real contribution bottom-up processes make
to successful and usable designs.

Unfortunately, many people and design-studios often lock themselves into
digital-diagramming tools and models because it makes them feel more
professional, offers a degree of intimidation over clients and
co-workers, and creates a proprietary language which cannot be easily
deciphered and therefore challenged (ie. a non-IA cannot comfortably
point-out an issue within a Visio diagram without feeling somewhat
over-their-head just because of the difficult presentation-medium.)
Within a whiteboard environment there are no 'rules' and things are not
set-up in any way which will upset a delicate boxes-and-arrows balance
(ie. you may erase and contribute at will, make the craziest and longest
squiggly-line-connecting-things as you wish, without facing obstacles ~
you just do it!).

Whiteboards as living, working, deliverables-in-the-making are more
capable, honest, and candid actually, (which is the goal), because they
avoid the projection of a professional occupation (unlike whipping-out
the PowerBook + OmniGraffle or FreeHand/Illustrator + digital tablet +
Ink hooked up to a projector to run circles around everybody). In the
whiteboard universe no one is afraid of stepping on a colleagues toes or
disparaging another's hard-work in front of supervisors or peers -- it's
just a whiteboard. This is the type of informal and candid atmosphere
which is so critical and important to early-stage design.