Home > Personal, Projects > Four requirements for successful development
23 May

Four requirements for successful development

Posted by 3 comments

At this stage, this is more a hypothesis… I want your reactions to this concept.

It’s based on my past successes and failures in projects/development. I, like all of us, have strengths and weaknesses in different categories, but for successful product developments, you need each… equally… at different times, perhaps, but constantly evolving and influencing the project.

ThinkListenBuildSell-fourneeds

Again, these requirements are in constant flux through different stages of the project, actively influencing each other.

Think: You have to have a creative, useful idea.

Listen: You have to truly listen/hear and adapt to wants/needs. From your community to stakeholders.

Build: You can talk. You can listen. But to have traction, you have to build something. A mockup, a demo or a working beta. Very much from the “show your work” model.

Sell: For journos, this is a new phase. But you have to promo your project… sell it to people. From your supervisor to actual investors.

I’ll try to write/explain more about this later… but I wanted to post this before I forget it… and I also want to collect reactions.

Categories: Personal, Projects
Tags:
  1. May 23rd, 2013 at 09:15 | #1

    I think “at different times” is an important bit here. There are probably plenty of product dev diagrams that treat this a little more like a flowchart than a Venn diagram, although it’s also more cyclical than linear.

    One idealized view might be something like:

    Listen > Think > Sell > Build > (back to the beginning of the cycle)

    • Robert
      May 23rd, 2013 at 09:33 | #2

      Cool! That said, I don’t think there is one linear process. I have often started with ‘think’ then went to ‘listen.’ Or straight to ‘build’ so I could show someone the idea to spark the ‘listen’ process.

  2. May 23rd, 2013 at 12:28 | #3

    Right, absolutely — In a really healthy agile cycle, there’s a lot of build > listen loops, lined up back-to-back and then with a bigger one looping around all of them

Comments are closed.
π