What is the strategy?

[jezzsantos]

We need solid validation that there is a market for this capability!

We already have most of the technical solution in some form (nupattern). We could rewrite in a more basic form a more cut down version to pilot.

We could canvas around potential early adopters, we can propose that someone influential uses it, we could use it for a high profile project and demonstrate higher productivity. We can do all these things and more.

We need to harvest some real use cases of it and demonstrate them so people really get it.

Since its a new capability (radical innovation) we can market it as a new way to a specific role: the tech lead or lead dev. We could name it such.

Then we could educate the market on what this role does and how we help them do it.

[jezzsantos]

We could call this project: leaddev or techlead. And give the impression that its a role specific tool that this role should be using to legitimise it.

[jezzsantos]

Stage 1 is to get a CLI going, and used in several known projects.

• At this point, we know that developers are using it (it is desirable)
• We assume right now that the motivation is: to save themselves tedious work in creating project structure and laying out components that are part of large patterns. They are avoiding tedious work.

Stage 2 build the Rider plugin that also uses local storage. Both CLI and plugin can manipulate same local store.

Stage 3 could be to build an online SaaS service to store patterns and toolkits and solutions, and enforce subscription based model