Intentionally not using multi-home

[ka_nishiyama]

Until now, I have been thinking about making active use of one of Asana’s biggest features, “Multi-home tasks to avoid information silos”.
However, the reality is that “task multi-homing” can often be difficult to use.
Issues with multi-homed projects:

• It is not clear which project is the main one. (Assign Primary Project for Multi-Homed Tasks)
• People outside the project can view and comment on it.

---

I think that intentionally not using it is also an idea.
How to set up Disabling multi-homing to fully lock down a custom field.

Reference post:

• Large-scale, cross-functional projects - English Forum / Use Cases - Asana Forum

I would appreciate your advice.

[Emily_Roman]

Hi @ka_nishiyama, good question! You can find the option to disable the ability to multi-home tasks from certain projects via the Project Permissions settings, see screenshots below:

This feature is available on Asana Enterprise and Enterprise+ tiers, as well as the Legacy Enterprise tier.

I hope this helps!

[ka_nishiyama]

Thank you, @Emily_Roman .

Asana has always thought that multi-homing should be used proactively, but we have seen cases where it doesn’t fit with the structure of real organizations, so we’ve been pondering what to do about it.

We will think about how to utilize this mechanism.

[lpb]

@ka_nishiyama, I can’t imagine a reason to consider intentionally turning off multi-homing or discouraging its use except in cases where there’s an underlying training deficiency or existing workflow design issues.

I’m not saying multi-homing should always be used, nor should you go out of your way to use it when it doesn’t help, but to remove it as a tool for potential use where warranted doesn’t make sense to me. Maybe you’ve run into things I haven’t been able to envisage?

Thanks,

Larry

[ka_nishiyama]

@lpb , I understand your point of view.

I wrote my image here.

Large-scale, cross-functional projects

Overview Use Asana to manage large-scale projects(Different definition to Asana projects) involving multiple departments, clients, and partner organizations. Premise Asana Features: Asana provides a wealth of tools for open, non-hierarchical communication. Real-world organizational features: Internal communication tends to be closed within each department. When interacting with other departments, information about one’s own department is often somewhat exaggerated. Challenge To effectively…

[lpb]

I’ll reply in this topic thread:

Large-scale, cross-functional projects

Overview Use Asana to manage large-scale projects(Different definition to Asana projects) involving multiple departments, clients, and partner organizations. Premise Asana Features: Asana provides a wealth of tools for open, non-hierarchical communication. Real-world organizational features: Internal communication tends to be closed within each department. When interacting with other departments, information about one’s own department is often somewhat exaggerated. Challenge To effectively…

Thanks,

Larry

[Richard_Tasker]

@ka_nishiyama

It is not clear which project is the main one.

1. The concept of a Main project is interesting to me and I would like to know if others use this type of approach?
   1. I manage tasks in a Prioritization project used for intake form requests. To me, this is my main project.
   2. I built portfolios for the other teams in our organization, so they can create their own projects and we can use Asana Reporting for dashboards that capture all our projects. (For this example, one team’s project will be called the BMX and another team’s project will be called Elevate.) To those teams, they each consider those to be their main project.
   3. During a weekly prioritization decision meeting, I add subtasks and assign subtask owners, and I also multi-home the parent tasks to the Elevate and BMX projects.
   4. Instead of managing subtasks, people add tasks to their Elevate and BMX projects and now we have tasks in those projects that are for the same thing as the subtasks.
2. If I were to not use subtasks, I would need to go in each team’s projects and add tasks that are unique to that team - not convenient.
3. If I promote each intake task to a project, instead of adding subtasks, then I lose the ability to multi-home.
4. It seems like the only option is to teach people to NOT add tasks to their project when they see a task that has subtasks. What advice do you have for me?