Why, how and what.
Good software is always used but never finished. I believe in the power of prototypes to answer specific questions during the process of evaluating the underlying business idea.
On the philosophical side, prototyping for me means to always have a zen-like curious beginner’s mind – free of any possessions, since it is clear that everything is in a state of constant change.
And this understanding, together with constant testing on real humans, is the only way to understand the customer as well as the very own business model.
How: Focus areas
- Building pragmatic MVPs and prototypes to help validate business models.
- Develop a technical vision for the company for a suitable and sustainable architecture.
- Scaling engineering and product after a successful funding round.
- Cutting administrative overhead and political games by bridging the gap between business and engineering – I speak both.
- Foster engineering culture by focussing on agile process for shipping and quality.
- Boost Engineering tooling – by introducing or improving continuous integration and continuous delivery tooling.
- Building high performance organisations through inclusivity and diversity.
What: Models of collaboration
- Develop a MVP / prototype by myself. (Technically I can do this in a number of areas: Cloud / Serverless Service, Homepages, Web Apps, Mobile Apps, Chatbots, Alexa Skills, CLI, ..)
- Represent the technical vision of the company to its shareholders and investors.
- Regular Product prioritization sessions to eliminate bullshit bingos by working strictly thesis / proof driven.
- Prototyping workshops, either for teaching methods or for direct application.
- Coaching existing developers to fit into their new leadership roles.
- Workshops with predefined goals to improve engineering processes or communication with management.
Whom: Use Cases
- Early stage startups with a good idea, but without seed money. A prototype costs only a few daily rates and helps in most cases to collect a seed financing.
- Financed startups without a technical co-founder, or a technical co-founder who want’s to focus on the business side. Coaching a developer into a leadership role helps to bridge this gap while not losing momentum.
- Small and medium-sized enterprises wanting to branch out through innovation.
Principles: my personal values – expressed through others.
Man is the sum of his experiences. In this manifesto I describe myself through the thoughts of others. These are not just detached quotations, but highly condensed knowledge, each with its own recommendable text behind it.
I like to find (a) simple solutions (b) to overlooked problems (c) that actually need to be solved, and (d) deliver them as informally as possible, (e) starting with a very crude version 1, then (f) iterating rapidly. >>
If you want to make something grand, don’t start with grand ambitions.
Get in the habit of simplifying.
Validate your market.
Launch uncomfortably quickly.
Perpetual motion. Just Do It. Make little steps every day. >>
The ability to perform deep work is becoming increasingly rare at exactly the same time it is becoming increasingly valuable in our economy. As a consequence, the few who cultivate this skill, and then make it the core of their working life, will thrive.
High-Quality Work Produced = (Time Spent) x (Intensity of Focus) >>
Seek wealth, not money or status. Wealth is having assets that earn while you sleep. Money is how we transfer time and wealth. Status is your place in the social hierarchy.
Fortunes require leverage. Business leverage comes from capital, people, and products with no marginal cost of replication (code and media).
You should be too busy to “do coffee,” while still keeping an uncluttered calendar. >>
I think it’s important if you’re a creative person, or aspire to be, that you don’t spend too much time aspiring or asking advice. Just get going and address what’s roaring inside you. >>
[..] a man who procrastinates in his CHOOSING will inevitably have his choice made for him by circumstance. >>