# Workflows - unable to understand implementation

**URL:** <https://community.temporal.io/t/workflows-unable-to-understand-implementation/9109>\
**Category:** Community Support\
**Created:** [August 8, 2023, 9:39am UTC](https://community.temporal.io/t/workflows-unable-to-understand-implementation/9109 "2023-08-08T09:39:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![antonio.perez](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/antonio.perez/32/2417_2.png) [@antonio.perez](https://community.temporal.io/u/antonio.perez)\
**Post date:** [August 9, 2023, 9:20am UTC](https://community.temporal.io/t/workflows-unable-to-understand-implementation/9109/6 "2023-08-09T09:20:38Z")

</div>

I don’t have all the details for your use-case but sounds like a good reason to have a parent workflow written by the team HROPS and having the IT team exposing its implementation as a child workflow

See more info here [Child Workflow Separate Service - #3 by tihomir](https://community.temporal.io/t/child-workflow-separate-service/4892/3)

---

_[View the full topic](https://community.temporal.io/t/workflows-unable-to-understand-implementation/9109)._