How to Build a Startup Culture — and keep great people

Three years ago, I started my life in the startup world. Meeting new people, endless coding, building products, and pitching to customers…

How to Build a Startup Culture — and keep great people
Photo by @jweckschmied

Three years ago, I started my life in the startup world. Meeting new people, endless coding, building products, and pitching to customers have become my daily life. What I feel most proud about and would love to share is not a successful startup story, but the team culture that we have built.

On numerous occasions, talented people have shown a great interest in joining our team after visiting us or having just one lunch with us! This makes me wonder, what is it that makes us so enticing?

So, I’ve started asking around. This post is based on my experiences. Especially, the following things:

  1. Joining the Techstars family gives me the opportunity to talk with hundreds of teams in different stages, from the different countries around the world. We are able to exchange information between several of the founders about the way we do things and I have discovered that every team has its own culture.
  2. Went through tough times and still stuck together. For a small company like us, there are a lot of reasons your company can fall apart, such as co-founder issues, a financial crisis, etc. With the limited resources that we have, a simple team retreat can suspend most of our business activities.
  3. Work closely with companies on different scales. I always like to mention that I want to have more understanding about their company culture. (Yes, we are still alive if you need to measure user experience.)

Why is it important?

Culture defines how we act. It’s extremely important to startups. In the same company, we expect team members to be creative, to be self-managed, and to be engaged. This way we can move fast and break things in the way that big companies couldn’t. Having aligned on culture also means that we are aligned on making decisions. It results in the efficiency of the team’s work.

Culture is the people

By default, it’s the people who sum up how you do things in an organization. If you are a team of two and you and your co-founder are always unhappy, then your team’s culture is “unhappy”.

Photo by @isabellwinter

There was a day, when an experienced and successful founder of an IPO company asked us,

“If your company was a human, what words would describe it?”

Co-founder A: “Discipline. I wanted to deliver great quality of the product, so I’ll say that discipline among my team is the most important thing.”
Co-founder B: “Trust. My customers and friends always trust me. I trust them too. Trust is the most important factor; everything should be built on it no matter what we do.”
Co-founder C: “Agile. My team moves fast and is open-minded to change. We see the trend; we build things and go-to market strategy.”
Team member D: “Empathy. I always put myself in the other’s shoes. Empathy makes people understand each other. I can use it to understand users, too. I can avoid making the product that people don’t want.”
Team member E: “Happiness. Starting a business is hard and painful. Since I can’t change that, I at least want to make sure that I am happy during the process. I am a positive thinker, you know?”

Well, this process kinda shows how your company culture might look like now. Start by simply asking your team members.

We know you can’t have it all. It’s not what you say, it’s how you act. As long as you observe what your team really does, some values will be highlighted and some will feel less important for now. So, don’t rush it. Let the team organically have its own culture.

For example, Techstars has the culture of #GiveFirst and well-delivered it to the startup community, which is what the Techstars companies actually do. Thousands of founders contribute in sharing experiences, mentoring, and connecting people to each other.

Honesty in what you say is also a good practice. You can’t use “positivity” if you are always mad and careless with your team member. And there is no proof that you will not be successful if your culture is mean, negative, and mad. Embrace it!

Internal Transparency

Being transparent is the first step. For some reasons, founders are usually scared to share “everything” with the team. However, how could the team possibly be on the same page if the information is misleading or not transparent enough?

Being transparent also means allowing people to make decisions. Founders should leave some decisions to the right people in the team and trust them. Making self-managed decisions does not mean getting all of the members’ agreement, but the expert and the people related. The decision-maker must take all relevant advice into consideration, but they can still make the decision. This is called the advice process.

With transparency, you may find out some decisions also include personal reasons. And that’s fine, because the team is all about the people and it strengthens your culture when you care.

Build on what you got

As we can see, co-founders and core members will significantly affect the culture. Based on this, you could do iterations of refinements — making it more than just a few words. Creating an expressive value and working on vivid visions. For seeking ideas, you can always look back to the answers that you already have:

Why do you do it?
What problems are you solving?
How do you do it?

Here are some good examples that I know of:

I bet there is more! Feel free to list more in the comments.

Wrap-up

Once your culture is obvious and concrete, I believe it’s easier to hire the talents with a similar culture. Great people usually have their own working style that they like and they want to work with great people. They’ll know if they can fit in or not. Explanation is unnecessary.

Lastly, if you don’t have a great product and the momentums along the road, no one can save you from that.

Read more

掌握幣圈脈動,告別 FOMO 的資訊自動化流程嘗試

掌握幣圈脈動,告別 FOMO 的資訊自動化流程嘗試

幣圈訊息瞬息萬變,是否常常覺得很 FOMO 呢? 常常一個小時不看新聞就可能錯過了新的趨勢或是有用的消息。因此,我嘗試打造一條「獲取資訊自動化流程」。我希望透過以下幾個步驟,將「從 RSS 收集內容 → 摘要與翻譯 → 儲存 → 在發文時快速取得重點資訊」的流程自動化或半自動化,讓我在想要發佈 Twitter (X) 貼文時,能有即時且經過整理過的資訊可供參考。 整體流程概述 目標流程:RSS → Apify → OpenAI → Airtable → Chrome Extension → 快速分享 * 取得 RSS 新聞來源:定期自動抓取最新文章列表。 * 解析並擷取內文(Apify):從原始頁面擷取重點文字段落。 * 整理與生成摘要(OpenAI):運用 AI 將冗長文章化為精簡摘要。 * 儲存到 Airtable:將標題、連結、摘要等資訊結構化存放,方便後續查詢。 * Chrome

最常見的 Git 工作流程 - GitHub Flow

一種簡單的工作流程,適用於快速開發和持續部署的小型專案。 流程 1. 始終從 Main 分支創建功能分支:bashCopy codegit checkout main git checkout -b feature/my-feature 2. 在功能分支中開發,並隨時提交: git add . git commit -m "Implement feature" 3. 開發完成後推送到遠端 git push origin feature/my-feature 4. 發起 Pull Request 並進行代碼審查: * 在 GitHub 上創建 Pull Request。 * 通過代碼審查(Code Review)。 5. 審核完成後合併到

測試驅動開發 (TDD) 與單元測試、整合測試的概念簡述

在現代軟體開發中,測試已成為不可或缺的一部分。不僅能幫助開發者捕捉錯誤,還能促進代碼的模組化和可維護性。本文將深入探討單元測試、整合測試的區別,以及測試驅動開發 (TDD) 的核心流程和實踐技巧,幫助你快速掌握測試的精髓。 也許 AI 程式碼生成工具,最能快速優化寫測試的開發時間。多少來學習一點測試相關的知識。 * 理解單元測試 (Unit Test) 和整合測試 (Integration Test) 的區別。 * 熟悉測試驅動開發 (TDD) 的概念。 單元測試 vs 整合測試 * 單元測試: * 適合測試邏輯簡單且內部不依賴外部資源的功能,例如算法、數據處理函式等。 * 主要用於開發階段,快速檢查某段程式碼的邏輯。 * 整合測試: * 適合測試業務邏輯需要依賴外部模組(例如資料庫、第三方 API)時的交互行為。 * 用於確認系統內部的協作是否無誤,通常在測試環境下執行。 特徵單元測試 (Unit Test)整合測試 (Integration Test)測試範圍單個模組或函式多個模組或系統的整合依賴性獨立,不依賴其他模組或外部資源需要依

PM 加速開發:ChatGPT 到 Cursor 再到 Windsurf 的體驗比較

我是技術背景出身的產品經理,十年前曾是一名寫 Objective-C 的 iOS 工程師。近年來,我利用零碎時間,結合 AI 工具,進行產品發想與概念驗證,並打造一些功能型網站。自 2024 年 6 月起,我的體驗大致可分為三個階段,以下是我的學習與心得分享。 第一階段:ChatGPT 助力,但流程繁瑣 最早是用 ChatGPT 協助產 Code,我一筆一筆貼到我的程式碼下。我要詢問怎麼改動的話,也要將程式碼貼回 ChatGPT,在大量的複製貼上等待的過程,非常慢跟耗時,瀏覽器也會隨著大量的文檔開始變慢。這時候,我從不會到能做出一個聊天機器人網頁,大概花一個禮拜。我也是在這個階段學會了如何用 Vercel 快速部署架站,還有基本的 Git 指令。遇到一點問題常常會卡關很久,要邊做邊學。 第二階段:Claude 加速開發流程 Claude