... | ... | @@ -21,3 +21,6 @@ There is not always a clear accountability on roles and responsibilities for pro |
|
|
Related "projects" get started in separate areas to address the same capability (outcome). Each "project" may only focus narrowly on the scope of the specific area it has been started within (e.g. Data Definitions) and interactions with related projects required to deliver a working capability (useful outcome) are inconsistent. This also creates confusion for members on where they might join in the dialog as a single capability gets worked in multiple subcommittee meetings.
|
|
|
|
|
|
There have been some attempts to address this by assigning various subcommittee liaisons to specific projects. This may be an opportunity to clearly document those roles and bring clarity.
|
|
|
|
|
|
## Related conversation happening in different subcommittee meetings
|
|
|
The same topics are discussed in difference subcommittee-specific meetings without overlap in people leading to siloed conversation. This can result in misalignment and confusion about path forward. |
|
|
\ No newline at end of file |