Archive for February, 2012

@phineasb. Sneakerheadvc.com @agileuxnyc

February 25, 2012

RPMs > Horsepower.

An investor

Talked about prototyping shoes, trying out sneakers on real kids. When the focus shifted to process, Nike started paying attention and bought them.

Learning a specific thing about a specific element. Like shoes w no laces. Iterated way to something that works.

[this feels like a gold rush. Lean is the new gold]

Web has returned to basics of customer development. Define a problem and iterate and push it out. Keep trying. Through that you create something customers love.

We all are responsible to work on changing mindset over skill set.

To max RPMs, mind set > skill set

1) unicorns / *: don’t care about users, what they know will work. Some one with vision drives at that. (Steve Jobs? For later pondering). They don’t listen to users. What happens instead is iterate on bad products. (Ha! Mentions Steve Jobs as exception).

[btw all slides]

Feedback that isn’t actionable (“can we make it pop”). Then time bomb(” not gonnna work”)

When we look at portfolio companies that do well is about understanding. Questions aren’t why doesn’t it pop, it’s what were you trying to achieve. It is -why- what did you expect user to do. You don’t prescribe answers you try to draw out thinking.

Getting feedback from people actually using the product. What’s first, prioritize in an office, then go out and watch people use and get frustrated. Totally re-prioritized features.

Hopefully at your company the visionary unicorn isn’t what moves the crowd but attest orbs he has invested in, data moves the behavior at the company. What are we measuring at the company?

Are or dashboards something that causes us tobask questions about the fundamentals og your business. [aha re: my secret product!!]

Everyone in company has to understand the goal of the company, all must be on board with removing friction in the organization and moving it faster.

Proactively push out in the organization and celebrate great product, celebrate other company’s wins. Make it tangible.

“turn this way to go faster”.

This is what this VC sees when things are going well, what they look for in new companies. Demand it gets done, o

@agileuxnyc Raw Notes on-the-spot; reflections later / @ericburd talk on rolling out Agile

February 25, 2012

First thing to note is there is a lot of interest in this conference. A line out the door kinda interest. Folks with stacks of tickets attending with teams of co-workers. I am overhearing conversations that people have come into town to attend this from as far as Pennsylvania.

A funny thing: the slide on the wall says logistics. This consists of a Twitter hashtag, WiFi info and coffee details (when the breaks will be). 😉 I am sitting by people from Nielsen, kind of interesting cuz they are all about data. Seems to be a pattern these days.

@boogie (Jeff Gothelf) is telling us they ran the conference itself as a Lean UX project, with a hypothesis (that people want a conference), iterations, user stories, etc.

First up, Eric Burd from The Ladders. Mentioned original conf was a 35-40 person meet-up, small.

Rolling out Agile in an organization. Set up the problem.

A business owner was not happy with the MVP. Thought original product that was too thin. We in the room “get it.”. We get Minimum Viable Product. We are talking to each other. How to get business people on board.

Issue with picking the destination vision thinking we will just pivot around.

The people in finance, sales, marketing, and rest of company. Shows tech and product off, practicing Agile / Lean product development. How to get them to buy in?

My a-ha: we are doing this at my company to some degree. (ps – worry re: risk if ID issues so stay a tad cloaked on this blog).

“Agile is about risk mitigation”
– won’t go to market with something people don’t want

Waterfall is about risk mitigation–and used in other parts of company:
Sales has deals, beginning middle end.
Marketing has campaigns.
Finance has budgeting cycles.
All behave waterfall because is risk management.

Showed waterfall for finance, marketing, etc.

Change happens when something needs to move: a fire or problem statement.

Ladders Started looking at morale of Dev team. Question is Dev team engaged? Are they happy? Producing best work of their lives? Survey Monkey of morale shoes before and after Agile – morale boost.

So start with problem statement.

Getting head of sales to listen to customers in focus groups do not happen. To sell Agile to execs has hired customers to come in and eat lunch and talk to execs about customer need for the product. Voice of customer is important but hard to get execs to listen, so? Have lunch!

Hearing out of mouth of Sales moves organization forward. If you get sales force to gather product issues, can use tat in Agile /Lean to move bar forward.

[What I love is the open-ness. No “secret sauce” thinking.]

Language is important. We need to discover their language sets. Instead of forcing them to learn language of lean. Talked about a Finance term called level-loading- which is actually a lean concept. So use their language.

Train Exec team. The Ladders did a personnae exercise w exec team. Goal was persons, but taught exec Agile. Shows what it means to do Agile.

Small Bites: Shall wins over Big Bang.

Ben Austin example for education reform. Convinced one school district to change. Parents Unionized and have bargaining rights. Created so much press the conversation changed. Buzz made it to legislature.

Perception Shift – Subway

February 10, 2012

Conductors change shifts at the Times Square 7 train subway stop that I take home. The conductor exiting this first evening had a body of a retired, but in-shape, defensive lineman and long dredlocks. The guy taking his spot looked like he had spent too much time under ground; pale and flabby, he’d passed away the wait time by the escalator on the platform with his finger deep inside his nose. I had been sickened but tried to feel sympathetic. Maybe he was catching the same cold as the one going around my office. Earlier I had a meeting with a guy whose nose was raw and pussy from running. My stomach turned despite wanting to feel compassion. Same pattern?

In any case the perception shift occurred for me when the conductors changed shifts.

I scampered in when the train doors opened (last stop the direction they’d been heading), and snagged my favorite seat, a corner, by the door. Easy exit. The door to the conductor’s compartment swung open and out swung the occupant. The big guy said jovially to his relief, “She’s all yours. Bring her back in one piece, okay?” and laughed deeply, good-heartedly, with paternalism towards his ward, the train, and, smiling, strode out onto the platform.

At that moment the role of conductor sudden expanded for me from a guy in a small space standing on a train to a ship’s captain, responsible for a huge piece of equipment, sailing her above Queens or diving deep below the city. Like a ship’s captain, they look after us, the passengers, minding our safety, encouraging us to stand clear of the doors, scolding us when we don’t.

Previously I had thought of the conductor role in a smaller way, as an almost mean bureaucrat. More the pale flabby guy than the engineer.

Then again today the door slid open and another athletic conductor called out to a passenger, bemused.

“You didn’t trust me about the diamond train,” he said to passengers, grinning. We are aboard a train marked “local” by a green lighted circle.

“Well we wanted to be sure the train stopped there,” they replied, in a bit of a surly tone.

The conductor shrugged, and with a laugh said, merrily, “Well maybe *I* won’t stop there!” I chortled and he glanced at me, eyes sparkling, “Kidding!” and slid the door shut.

The passengers were like me, not realizing they are on the enormous version of Thomas the Train. They thought the guy announcing stops might not know whether he stopped at their destination or not. They didn’t realize he is…The Conductor.

Reflections on the Webcast and Raw Notes: Conversation Between @ericries , @zachnies and @rallyon- @rallydev – #agilenewlevel

February 2, 2012

At work we decided to watch a very interesting webcast of a conversation with Eric Ries and Rally Software’s Founder Ryan Martens and CTO Zach Nies.  Eric Ries is the author of Lean Start-up, currently holding the 9th spot on the New York Times best-selling business book list; Rally specializes in software to help with Agile Development, kind of a Basecamp for Agile – if you’re a PM and know what I mean by “Basecamp.” For those who don’t, these are online tools for managing projects, tracking deadlines and to-do lists, etc.

I had just been talking with someone in the morning about the need to change mindset within companies to really find a way to “Work Different.” There’s a challenge with teams in getting folks to understand it is safe not to be told what to do at every step of the way.  What went unsaid in this conversation was brought out in the Lean/Agile webcast.  It all comes back to not feeling like you might lose your job if you take a risk.

The same idea about mindset came up in this webcast conversation as it relates to the entrepreneurial propensity towards taking risks.  The interesting dimension they discussed is what we, in the PM world, call “risk management.”  Meaning, when you’re facing the chance that all could fail and you want to say “I’m scared that [x condition] will cause [y result],” you say instead “There’s a risk of [y result] and here are the ways we can mitigate that.”  Risk management might not lead to innovation.  This is because the very hypothesis behind risk management is that you can and should head off failure.  With that approach, no wonder folks are scared to take a chance and try things.  Seems obvious, right, they don’t want to take the risk.  It comes back to a willingness to learn and to see past failures in Corporate America.
(more…)