Software Architecture IS Conway's Law

You have to talk before the work starts. Get together and:

• identify all the moving pieces • split those into components • define clear interfaces • agree on the contracts

Then you each go build the individual pieces. Good code structure and clean architecture happen automatically as a function of splitting up the work.

I think the trick is to break down the work. With or without a team.

You have a goal, how do you get there in a series of steps?

After each step the code should work, be shippable, do something valuable, and get you closer to the goal. The smaller the steps, the cleaner your architecture will be.