Archive for the ‘Lean’ Category

@jboogie @agileuxnyc Demystifying Design #leanux #demystify

February 25, 2012

Wow, doing a presentation while organizing conference. An example of hyper productive. 🙂

Started his career working at Circus. Had to figure out the culture. Used example of Sneetch. In one end goes requirements, other end comes Sneetches with stars on their bellies.

We like it like Wizard of Oz. Insulates us from Them. Mass can adore us from afar.

But it becomes a cancer. Everyone splits off into silos and no communication.

Everyone starts using different language. This puts PM in middle, (used Frodo as PM! 🙂 )

Transparency builds trust. Because they know what’s going on.

Robert Dailey study in Management Daily – how tight is the team. (reminds me of a tech lead saying to me “we getting the band back together?”)

Show how sausage is made.

Learn Design is a balancing act. When people collaborate, their investment goes up and quality of work goes up.

(Oh no! WordPress crash)

UX becoming facilitators.

Sometimes okay just to reveal it was just gut.

Architect for the Eden Project. Ground is being quarried. Look for TED talk.

Marc Scheff

Typekit – showing font affect right away

1 draw together
2 show raw work don’t wait for ta-da, walk them thru process
3 teach the discipline – every time you show work, teach rationale and decisions, teach the jargon
teach jargon, examples KERF carpentry, sanguineous crust is a scab, cognitive load
4 hang the work in the halls

Advertisements

@neilw @agileuxnyc how design works @betaworks raw notes

February 25, 2012

Invest in companies (like Twitter, Tumblr, Kickstarter)

Build companies, but not an incubator

Think of themselves as stem cells for Internet

Right now focused on Big Data + real time + social

Cameron Cauzon (sp?) wrote about designer stack.
UR
IxD
VisD
CSS

Specializations across mobile

Have skills not roles. Jump into spiral and do.

Give a 100-day window to build something end-to-end

(Oh-HO they invested in SocialFlow)

Break up products into smaller parts

See New Yorkers article on Pixar.

Firefly for clicking and chatting on site. But quality of discourse would, um, degrade as it was real time and if lots there at same time.

Bloggers understand short online life of bloggers, and very slow traffic numbers.

Realized nyt writers really had a need for a dashboard of timed metrics on blogs.

(btw – I am sitting by two folks from a startup bought out by Nielsen.)

Model and iterate

-sketch and iterate, everything is a transitional document

– has a grey real-timey scroll of events, feels alive

Culture matters- want people who get that UX is collaborative, and jump in

demo culture
– every Thursday different team demos

Showed SocialFlow’s Graffitti of 2 train to express culture, open space, hacker culture

Design is how it works – Steve Jobs. — no above or below the line

@zakiwarfel talks about Design Studio @agileuxnyc raw notes

February 25, 2012

@jeffpatton mentioned again

Tips for Design Studio

-use butcher paper and Painter’s tape; use sharpies
-graph paper
-team members with teams, get scenarios and one of the personas
— do not use all designers, etc. Use people from each expertise, business, UX, tech particularly
– most important tool is stop watch — likes Top Chef’s Quick Fire challenge

Has a grid system to use with block at bottom – do 6 to 8
To warm up, have them sketch stuff quickly using pencil, like circle, square and show to workshop–also levels everyone

Everyone is equally uncomfortable regardless of place in hierarchy

Goal is just enough idea to pitch to team members, and don’t have time to details

Only get three minutes to pitch.

Elect a team member to pitch to another team.

Hyper Island did this in our Master Class

Feedback can tend to I like / I don’t like

A critique is did they accomplish goal?

2 minutes to provide 2 to 3 ways design accomplished goal and 1 to 2 ways. Whether you love or hated it. Doesn’t matter. Use red to mark oops and green to what works.

Stealing is highly encouraged.

If you rip it off, have to make it better.

Generate six weeks of work in six hours. So costs? Costs less!

@andersramsay #agileuxnyc raw notes on collaboration talk #agile

February 25, 2012

UX Rugby

Says he is an Agile UX Coach. Makes me think of @Tobiasmayer vpcurrent Twitter thread that is “against” coaching

“Feeding the Beast”. Devs delivering features faster than can design

“Half-baked UX” – product owners pressured into get anything that functions out door.

“Sprint Tunnel Vision”. – and delivering an incoherent product

Why? A lot of UX designers playing Waterfall game on an Agile playing field. designing a Sprint ahead – is waterfall.

Lacking tools to understand how Agile game is played.

@totheralistair mentioned Collaborative Game book….

Mentioned Nonaka and Takeuchi’s New, New Product Dev paper

Compares Waterfall to Relay Race. Game is not designed for support

Rugby is intensive, continuous, with collaboration at the core

– reach goal line again and again to win game

Moved to concrete examples

Showed a meeting, like those we typically attend with a one-way, broad cast, meeting presenter. (but that is us now! Unfair, I know).

Then showed a workshop.

In a workshop you can rapidly iterate a shared understanding

Ideation Clearinghouse (like Design Studio).

Talked about a case of a CMO who just sat in on a waterfall design review in which he shut down product after saying designers did not understand his requirements

Do warm-ups. Card storming.

Sketching in a time box – with no rules – not even that they must draw. Can write.

Critique. Pay attention closely to what you are seeing if facilitating. Look for exceptions. Can uncover vision differences quickly.

Learn, apply and recombine workshop patterns.

For stuff that takes sitting down, do pairing. Showed cool yin-yang pairing desk.

Showed snapshare method. Paper prototype/wireframe to build / HTML CSS

Mindset – copied HSBC ads on mindset showing rugby vs relay race

Learning to play passing game in a collaborative manner.

Q: how do we estimate in planning meeting
A: no magical answer – make sure element of sketching in place before estimating. Have a few sketches

Have business sponsor do the elevator pitch of what the problem is we are trying to solve

Five minutes best time box

Only strong survive. Only stuff that achieves goals – devs excited, bus people figure out how to talk to engineers

Prepping room. Put up Butcher paper sheets and each team gets packet with persona.