Skip to main content

๐Ÿค First Month Meeting Collection

ยท 4 min read
Lucy
Co-Founder of SAD-AI

Our first entrepreneurship meeting where we quickly decided on several important matters

Let me briefly explain our division of work and approach for the entrepreneurship journey.

Division of Workโ€‹

Zane A technology enthusiast with passionate dedication and an engineer's soul for technology, naturally taking charge of technical architecture and planning.

All kinds of technical knowledge and innovations can't escape his knowledge exploration radar. Sometimes he plays a key role in calm analysis and judgment.

When I'm hesitant and indecisive, he boldly makes decisions and we bear the consequences together ๐Ÿ˜†.


Lucy Mainly handles any management, organization, marketing, copywriting, project management, and communication tasks. Also a frontend engineer.

Following Zane in learning technology, I'm more of a "package integrator" - good at using and integrating, and when encountering problems, I quickly find solutions.


If we rate technical skills from 1-10, I'm about a 6; Zane is a 9.

If we rate management skills from 1-10, I'm about a 9; Zane is a 6.


This is how we established our division of work. We each have our strengths, learning to collaborate and work together to achieve our goals. ๐Ÿฅธ

Zane develops the main framework, while I work within that framework, taking notes while developing.

Meeting Approachโ€‹

We have a fixed weekly meeting schedule, and when there are more items to discuss, we arrange additional meetings.

Each meeting is fixed at 2-2.5 hours, with one Sprint per week.

Meetings mainly discuss tasks to be executed that week, and we also decide on solutions for content prepared before meetings.

We don't waste any precious time, because we each have other life priorities to attend to.

While entrepreneurship is certainly one of the dream list items we want to try in life, we won't neglect other precious people and things in our lives.

So our meetings are focused and concentrated - discuss, decide, reflect, and proceed with meeting priorities with swift decisiveness!

20250218โ€‹

In our first meeting, I had already organized the items to be decided beforehand, such as:

  • domain
  • official website content
  • product MVP features
  • timeline planning

When we both lack ideas, we're both the type who suffer from choice paralysis.

This meeting, we spent the most time deciding on the domain name.

Because our original name had already been taken, we listed several combinations,

and considering SEO factors, we really didn't know which was best.

Finding a suitable domain took about 30 minutes front and back, which was quite long, and our indecision left us feeling lost.

So we used the elimination method, leaving three suitable names,


Then! We used a spinning wheel to decide - whichever name the wheel landed on, we'd buy that domain! ๐Ÿ˜Š

This saved us a lot of energy ๐Ÿ˜…


Other items were also smoothly discussed and suitable approaches were found. The lesson learned that day was:

When you're indecisive, leave it to the spinning wheel!

20250225โ€‹

This day we discussed:

  • UI Mockup
  • Transferring the initial website to a new account
  • Deciding on project management tools
  • Reviewing MVP feature feasibility assessment
  • Establishing Discord channels
  • Tentative product logo

Since we're both usually very busy - one busy caring for family and getting certifications, the other busy with exercise and life management.

This day's meeting, Zane very quickly handled the GitHub repo and GitHub Actions to a good point.


Next, we discussed whether to switch from our original ClickUp to JIRA and Confluence for project management.

Finally, considering familiarity, interface readability, and cost, we decided to abandon ClickUp.

Because time is most precious to us. The most important thing is to move the project forward first.

20250227โ€‹

Discussed:

  • Tasks to complete for the week's Sprint
  • Continue adjusting the product website's CI/CD
  • Adjusting Discord channel naming conventions and permission settings
  • Surveying language frameworks

This day's meeting was less than 2 hours, and we quickly listed all the items that needed to be listed clearly. Then it was time for execution and completion.

Once a choice is made, don't look back wondering if it's right. Just make it right!