Well, it has been a long time since the last entry. And so much has happened, the birth of groupDNA and as a spin-off tickerTXT. What was a what if idea has become the main focus. The team has grown to 4 co-founders. In June we won the Berlin Seedcamp, in July we were awarded a special prize at the Hasso-Plattner Ventures Social Entrepreneurship Event. In August we got the ok for support by the Zukunftsagentur Brandenburg (ZAB). In September we had an incredible week at the London Seedcamp final - one of only 23 startups, selected from several hundred applicants...
This week and the next will be quite interesting as well. There have been some nice meetups leading up to next weeks web2expo. I met the Amazee founders Dania and Gregory Gerhardt.
[caption id="" align="alignleft" width="200" caption="Barcamp3 Berlin"]
[/caption]
I am really looking forward to finally be able to attend a barcamp - this weekend in Berlin. If you are quick, the registration reopened, so go for it. A couple of weeks ago, the list seemed complete.
I am thinking of suggesting a subject close to my heart. The principles for group technologies. For a long time we assumed group applications had to be technologies with an emphasis on function: communication, collaboration, coordination... Contact management, time and planning applictions... We now are moving from functional software to functional web services. The web has led to relatively few really interactive new group services, they were just better than the old device centric software.
APIs are an afterthought of quite old-fashioned platform designs: facebook is an open company directory, Salesforce is a virtualised SAP world.
A few thoughts about service design principles for infromal groups based on sociology, anthropology, psychology and observations:
Groups are
This week and the next will be quite interesting as well. There have been some nice meetups leading up to next weeks web2expo. I met the Amazee founders Dania and Gregory Gerhardt.
[caption id="" align="alignleft" width="200" caption="Barcamp3 Berlin"]
[/caption]I am really looking forward to finally be able to attend a barcamp - this weekend in Berlin. If you are quick, the registration reopened, so go for it. A couple of weeks ago, the list seemed complete.
I am thinking of suggesting a subject close to my heart. The principles for group technologies. For a long time we assumed group applications had to be technologies with an emphasis on function: communication, collaboration, coordination... Contact management, time and planning applictions... We now are moving from functional software to functional web services. The web has led to relatively few really interactive new group services, they were just better than the old device centric software.
APIs are an afterthought of quite old-fashioned platform designs: facebook is an open company directory, Salesforce is a virtualised SAP world.
A few thoughts about service design principles for infromal groups based on sociology, anthropology, psychology and observations:
- Groups are best in relatively small numbers with little or no hierarchie
- Groups are heterogenious - there are always minorities, groups need to differences among their mebers to exist
- Groups are inclusive - they embrace normally new members, they normally do not exclude people for "technical" reasons.
- Such groups have no purchasing power - they normally don't have a budget. Every commercial decision is tedious because because of that. 100,000 € employees are suddenly discussing about pennys. The smaller the budget, the worse.
- Technology for groups has to be seamless, unobstrusive.
Groups are
Comments
Post a Comment