Wednesday, April 24, 2013

Reporting technical Issues: The Quick, And A Developer

If Your Main Task Isn't Developing Code, But Positioning It (selling its usage (seats) to Enterprise customers), then you might have a tendency to report issues, as they emerge. In quick emails, like the feed of information rapidly, like from a battle. It is too quick.

If Your Main Task Is Developing Code, And Not Selling It (positioning its usage value (clicks) to Enterprise customers), then you might have a tendency to ask for details. From the quick. And the more details. It fills your story, the... investigation.

The quick: from the field, to the point, meta... "HAVE YOU EVER SEEN THIS???"

A developer: stories, "tell me, precisely what happened, browser, clicks, versions, user persona, sales value...

Great software can emerge when the passion of the user feedback meets the developer craft - sales revenue + usage value

Anyway, something I thought of today... And learned from a co-worker and good friend.

No comments: