Clay Tech

"clay-works make things real"

translated from clazytech.com

Seven Rules For Launching A New Project, Before You Start

This is a slide deck I made a while back. A friend brought it up recently, and rereading it, I found it held up surprisingly well, so I’m transcribing it here. https://www.slideshare.net/qzuryu/ss-44468259


What follows are seven points summarizing the ideal organizational structure and mindset for driving a “startup” or “new project,” drawn from my time moving between large corporations and startups.

There are plenty of industries and exceptional cases where the premises here don’t apply. I’m setting those aside.

① Flexibility

Understanding toward pivots – The more legitimate pivots, the better – However, don’t do a “table flip” (more on this below) A small, nimble human resource pool – Build a team of generalists rather than specialists. Ideally, every single member would individually have enough development ability to productize something alone, even left to their own devices Don’t fix the platform – This goes beyond technical choices like the OS, processor, sensors and other key components. Keep outsourcing partners and carriers unlocked too, as far as possible, and move the project forward without committing early

② Prioritize speed

Run through many trials and errors and push toward a solution – In other words, just try it first Build an experimental PCB and write test code before writing a spec document – The spec document is for communicating with external companies, not for getting internal approval – It’s fine to have that discussion once the experimental prototype is up and running Don’t spend time and money on things whose effectiveness is hard to measure – Website maintenance, advertising, exhibiting at trade shows with unclear intent, and so on – If you have time for that, write one more line of code, run one more proof-of-concept test, and talk to one more user, potential user, or component manufacturer

③ Prioritize efficiency

No meetings other than discussions and brainstorms – Reporting and sharing should happen within everyday conversation (in person or digital, doesn’t matter) – Don’t let the team grow to a size where that’s impossible Throw out the concept of a normal work schedule – A good engineer, if constrained, will work exactly 240 days a year (the number of working days for a civil servant). Unconstrained, that same engineer will work 365 – Office hours, overtime, working on days off, paid leave: treat all of these as if they don’t exist – Remember you’re working project-based, not hourly – Allow remote work and WFH. If that results in nobody showing up at the office, the project is already dead (actually, that’s a good barometer) Introducing a business efficiency system almost always makes things less efficient – The simple answer is to use the tools everyone already uses normally – Google Apps, Evernote, Dropbox, Facebook, and so on

④ Centralize information

Keep reporting channels as limited as possible. Ideally, everyone reports to one single person without exception – Dispersed information is what trips you up at the critical moment – This should be achievable at least while the organization is 10-20 people – That reporting target has a pretty tough job, but it’s an extremely important one, and they should carry it out with that awareness Managing things through periodically submitted documents is a manager cutting corners, and it makes the whole operation less efficient

⑤ Don’t do table-flip pivots

Pivots are necessary. They’re important, in fact. But a “table flip” — resetting everything — amounts to endorsing a waste of time and money – You can do that, but it belongs to the scenario where you dissolve a department and the person in charge takes responsibility. It might go well afterward, but by then it’s already a different company, a different project – That said, straining to manufacture a pivot that merely looks reasonable is also a mistake. If you’re only thinking about it once the moment arrives, it’s already too late Take the flexibility described in ① seriously, so a healthy pivot stays possible – Always keep a few options clearly laid out – Once a project gets moving, tunnel vision sets in. That’s obvious. So err on the side of being overly cautious about it

⑥ Chemical reaction

Gather a team with as many different roots and careers as possible – Synergy is born just from people in different industries talking to each other (that’s how a certain startup grew) Once the team is formed, put effort into cultivating chemical reactions within it – Networking events are exciting, and it’s tempting to keep doing them, but what matters most, first and foremost, is the internal dynamic Freedom of tool choice – Let each member choose tools according to their own preference. The growth that comes from that becomes an asset to the organization

⑦ Think deeply, but don’t build deeply

Think hard about the spec. A major overhaul of the spec after release almost always means a loss But don’t build it out in depth. That belongs to companies that already have a brand, and it doesn’t suit a startup – This is only permissible in markets with vast stretches of time, or situations with no rivals. No startup has succeeded in a market like that – Thinking is free. Building things out in depth costs both money and time Countless things took a long time to build out in depth and still sank because the finished quality was mediocre. And just as many things launched to a chorus of “come on, what is this, lol,” then gradually gained acceptance and rose all the way to becoming the de facto standard


Originally published in Japanese at https://clazytech.com/2015/02/334/. Translated with LLM assistance and reviewed before publication.