Friday, October 16, 2009

Productizing_kraka

Lab: Technology Prototypes

Research laboratories produce scientific findings and 'raw' lab technologies in the form of demos or "technology prototypes".


Lab technology is often entirely orthogonal to the product that will emerge from the process of successful technology transfer.
Nevertheless, we see many labs spending huge amounts of money and effort to investigate the marketability of their technology prototype as a product.
But a
(lab) technology prototype is rather an aspect of a product still to be discovered.

A research
finding is NOT a product; a research result - in due time - may become part of
one or more different product.




Transfer: Usage-informed Prototyping, the process of 'discovering the product(s)'


The technology transfer process is really a process of
identifying and choosing between promising ways of "packaging" the
research result with other emerging and mature technologies into something that
provides discernible value to people using them.






Usage informed prototyping adds value to the
technology, transforming unfit technologies into fit ones.
Some resulting product
concepts point to market opportunities that are outside the main stream of the
technology creator's primary business, that is, they could become likely
candidates for licensing.




Most interesting systems need to evolve during
development
- and after deployment. Watching an emerging technology in the
hands of users is a powerful source of inspiration, made possible by robust
prototyping of the [user experience] design.


Pre-Productizing: Designing Product Concepts

Define the major user affordances of the technology
Identify and analyze plausible and sufficiently important usage domains where such affordances are likely to be important.
Build and design a robust technology prototype to be deployed in the most promising usage domain.

Watching an emerging technology in the
hands of users, in a process of "Constructive Deployment".

Discover product and service opportunities from observation of real behavior.
Observe early contingencies in the usage environment that can be deftly translated into opportunities.



(a) Survey: If any prior work exists on
markets, competitive analyses, etc., the survey will leverage such knowledge
but also complement it by applying a
usage-centered analysis.



 



(b) Concept Building: provides you with a data based value proposition for one or more
re-configurations of the technology,
provides a "sanity check" with respect
to usage impact of such product concepts (may go direct to (d))



 



(c) Constructive Deployment: In return you
will get both an improved product concept and a substantiated value proposition
with data from before and after.
... It is much beneficial for the
final product concept when the study of the work practices has impact on the
(re-) design and packaging of the technology.


(d) Pre-product: improved product concept, substantiated value proposition, usage-validated
requirement specification (and research data) for handing over the technology to licensees or transferring it
to product development & marketing.
















Friday, March 13, 2009

cornet_gdocs_index

Here are the Links to the Open Documents that contain the current state of the (old) Proposal Text:

(For each chapter there will be one Google-document. The Old Proposal Text Building Blocks can be freely edited.
For the new draft text of the CORNET Full Proposal there will be fresh documents added here, again for each chapter.)


Evaluation Report (Click on link, add your thoughts)

000 | Old Proposal: Project Title (Click on link, add your thoughts)

001 | Old Proposal: Abstract (Click on link, add your thoughts)

002 | Old Proposal: Focus of the project (Click on link, add your thoughts)

003 | Old Proposal: Objectives of the project (Click on link, add your thoughts)

004 | Old Proposal: Scope / SME 2.0 graphical overview (Click on link, add your thoughts)

005 | Old Proposal: Old Workplan (Click on link, add your thoughts)

006 | Old Proposal: Old consortium description (Click on link, add your thoughts)

007 | Old Proposal: European innovation impact on SMEs (Click on link, add your thoughts)

008 | Old Proposal: Economical impact (Click on link, add your thoughts)

009 | Old Proposal: SME Innovation Community (Click on link, add your thoughts)

010 | Old Proposal: Exploitation (Click on link, add your thoughts)














cornet_gdocs_index

Here are the Links to the Open Documents that contain the current state of the (old) Proposal Text:

(For each chapter there will be one Google-document. The Old Proposal Text Building Blocks can be freely edited.
For the new draft text of the CORNET Full Proposal there will be fresh documents added here, again for each chapter.)


Evaluation Report (Click on link, add your thoughts)

000 | Old Proposal: Project Title (Click on link, add your thoughts)

001 | Old Proposal: Abstract (Click on link, add your thoughts)

002 | Old Proposal: Focus of the project (Click on link, add your thoughts)

003 | Old Proposal: Objectives of the project (Click on link, add your thoughts)

004 | Old Proposal: Scope / SME 2.0 graphical overview (Click on link, add your thoughts)

005 | Old Proposal: Old Workplan (Click on link, add your thoughts)

006 | Old Proposal: Old consortium description (Click on link, add your thoughts)

007 | Old Proposal: European innovation impact on SMEs (Click on link, add your thoughts)

008 | Old Proposal: Economical impact (Click on link, add your thoughts)

009 | Old Proposal: SME Innovation Community (Click on link, add your thoughts)

010 | Old Proposal: Exploitation (Click on link, add your thoughts)














Thursday, November 20, 2008

Lev Manovich's new book

"Software takes command" (pdf), here

"The new social communication paradigm where millions are publishing “content” into the “cloud” and an individual curates her personal mix of content drawn from this cloud would be impossible without new types of consumer applications, new software features and underlying software standards and technologies such as RSS. To make a parallel with the term “cloud computing,” we can call this paradigm “communication in a cloud.” If “cloud computing” enables users and developers to utilize [IT] services without knowledge of, expertise with, nor control over the technology infrastructure that supports them,”169 software developments of 2000s similarly enable content creators and content receivers to communicate without having to deeply understand underlying technologies."

Enterprise 2.0 (short) - Dion Hinchcliffe

    * Freeform: Only minimal upfront structure, with simple lists, tags, and microformats at first, with more structure later if absolutely needed.
    * Zero Training/Simple: Any barrier to use means that automatically fewer people will use the application or its more complicated features. The most successful sites on the Web require no training at all and guide the user to do the right things.  Your business systems can and should be similarly effortless to use.
    * Software as a Service: Online software, with its functionality and information available on any computer, home or work, anywhere in the world, day or night, is the most productive and useful software possible.  Installed native software just cannot compete with such persistent availibility.
    * Easily Changed:  If a user can’t easily make the necessary change to the structure or the behavior of a system, he or she must have an expert — usually in the IT deparment — to do it, and get in line to wait for it, not to mention pay for it.  This simply won’t do when there are ways to put much of this control back in the user’s hands.  Using the structure of the Web to chunk up functionalty, the increasing use of feeds, badges, and widgets, will transfer many common IT tasks back to end-users in the next few years.
    * Unintended Uses:  Preconceived notions about how an IT system will be used can cut it off from the most valuable uses down the road.  RSS syndication is teaching us a lot about this phenomenon on the Web, as well as mashups.  It’s all about letting the structure and behavior of IT systems emerge naturally and organically. Having open APIs, easily wired together pieces, and loose and fluid tools helps enable this as well.  Discoverability of all of these is essential too.  Examples:  Not UDDI, search.  Not Web services, RSS. Not portals, widgets.
    * Social: Business software tends to harness collective intelligence and even e-mail is social to a certain degree (but darn it, it’s push isn’t it?).  Enterprise Web 2.0 software enables pull-based systems that enable people to come together and collaborate when they need to and are entirely uncoupled when they don’t.  Enabling just-in-time, freeform collaboration is the key, and so is capturing and publishing the results to be reused and leveraged afterwards by others.  Wikis combined with enterprise search do all this automatically for example.

http://blogs.zdnet.com/Hinchcliffe/?p=57

July 26th, 2006
Enable richer business outcomes: Free your intranet with Web 2.0

FAQ E2.0: Was ist "Enterprise 2.0", ganz kurz?

Eine radikale Umpolung: Alles, was ein Unternehmen tut, findet dann per default nicht im geschlossenen Kern der Organisation statt, sondern im Web - (a) im halbgeschlossenen Netzwerk-Web (Team/Projekt-Mitarbeiter), (b) im halboffenen Netzwerk-Web (Projekt-Partner, Communities of Interest), (c) im WildWildWeb selbst (offener Informationskreislauf, als offene Konversation mit Märkten/Kunden).

Erst dann wird festgelegt, was im geschlossenen Kern (Sicherheitszone) statfinden *muss*. Also Maxime:
"So viel wie möglich der Unternehmensprozesse im offenen und halboffenen Web abwickeln, nur so viel wie unbedingt nötig im geschlossenen Kern."

Der Sinn: Die enormen eigendynamischen Netzwerk-Effekte nutzen, die das Web bzw. Web 2.0 ermöglicht, um Mehrwert zu erzeugen, der sich am Ende irgendwie auszahlt.

Merksatz: Web 2.0 ist Vernetzung als Prinzip - technische Vernetzung über das Web, soziale Vernetzung über Social Software, Informations-Vernetzung über (im weitesten Sinn) semantische Software.

FAQ E2.0: Was bedeutet das für KMUs?

KMUs sind aufgrund ihrer besonderen Struktur eigentlich prädestiniert für "Enterprise 2.0": flache interne Strukturen, Flexibilität und Schnelligkeit, Grenzen Privat/Arbeit verfließend, komplex ausdifferenzierte Organisations-Prozesse sind de facto zu aufwändig, Vernetzung nach außen (Partner, Märkte, Branche) ist immer ein entscheidender Wettbewerbsfaktor, kollaborative Projekt-Vernetzung mit anderen KMUs ist in vielen Branchen eher Normalfall als Ausnahme.

Die allermeisten E2.0 Tools sind von innovativen IT-K(M)Us für die eigene Arbeit erfunden worden! (Paradebeispiel 237Signals, aber das gilt ganz allgemein).

Aber bis jetzt wird E2.0 paradoxer Weise fast nur in größeren Unternehmen (> 250) als strategisches Thema betrachtet, weil nur die sich Experimente in abgegrenzten "Spielfeldern" leisten können (oder leisten zu können glauben).

"Enterprise 2.0" - ist das nur "Social Software" oder betrifft das auch 'klassische' Business-Prozesse, die bisher mit geschlossener Enterprise-Software (SAP, MS usw.) abgedeckt werden?

Hier muss man eben den kritischen Kern, also die Sicherheitszone des Geschäfts, genau identifizieren. Diese ist NICHT geeignet für E2.0. Das betrifft sicher die Abwicklung von finanziellen Transaktionen, auch Planungenund Kalkulationen.