Hi @jla1234
In short my view is yes you are overcomplicating it. I would start small and build up as you get used to Asana and how you and your partner work and collaborate together.
The more projects and teams you have the more rework you may have to do when you adjust to how you work together.
Here are some good post to give you more clarity.
“Should I make this a Project or a Team?” This question, and others like it, comes up often when starting something new in Asana, for both novices and experts alike. And it’s really just the tip of the iceberg.
How can you envision the structural, big-picture view of what you want to accomplish and translate that into an architectural framework in Asana that will enable your workflows, processes and information repository needs durably and flexibly, now and as they scale?
Asana often provide…
Hi,
:question:I often have the opportunity to evaluate my client’s Asana “systems” and share my insights: do I believe their system is good? Can it scale? Are they gonna hit roadblocks soon? Can I suggest better?
For years, I based my judgment on my personal experience and my gut feeling. I never had the intention of formalizing that approach. But after all, that makes sense. If I could turn that gut feeling into a real framework to evaluate someone’s system, then I would be able to give actio…
Hope this helps and enjoy your journey.
Jason.
4 Likes