# data[].attributes.headline
Dedicated employment queries team not involved in implementation work?

# data[].attributes.subject
Dedicated employment queries team not involved in implementation work?

# data[].attributes.headline
How would DOPP structure OPPD if she was building the team from scratch, ignoring actual warm bodies?

# data[].attributes.subject
How would DOPP structure OPPD if she was building the team from scratch, ignoring actual warm bodies?

# data[].attributes.body
We've been talking about it but really need to look into proper system for km and make conscious effort to upload final positions in correct eRegistry folders

# data[].attributes.headline
Central repository of FAQs/ Case studies

# data[].attributes.subject
Central repository of FAQs/ Case studies

# data[].attributes.body
1. Teams to contribute to repository of FAQs. To provide ease of access new or existing FAQs on LR related policies for a quick reference for OPPDians

2. Case studies (if any)

# data[].attributes.body
Team is constantly grappling with new info and new decisions and needs higher efficiency on how we work including on pulling up past positions and discussions quickly. Wonder if we need a dedicated project vs as an additional side hustle for officers.

# data[].attributes.headline
Dedicated team for employment queries and KM

# data[].attributes.subject
Dedicated team for employment queries and KM

# data[].attributes.body
Yes I agree that it would be good to have a dedicated team that handles employment queries moving forward and liaise with ESE, ODCS, TADM or TAFEP where needed. This will also make KM easier. It would also be great if we can have one or two LSD officers attached to us as that usually takes the longest time.

# data[].attributes.body
Regardless of how the team is structured, it’s important to have platforms for collaboration and a community of sharing. A town hall can serve as a space where different sub-teams stay informed about key developments, align on goals, and exchange ideas.

# data[].attributes.body
I wish thirdsight works in MOM. It is useful coz I can find previous emails from keyword search.

# data[].attributes.body
OPS handles some employment queries which overlaps with OPD-WFE's queries - think it's ok to continue with this given the load of queries received and from diff sources too (ODCS, tripartite partners, unions, etc) but perhaps for efficiency, queries can be sent to all of us within OPS/OPD-WFE and we can keep each other in the loop when clearing replies, so we are aware of the latest position/discussions and share the KM folder as well (which should be easy and intuitive to use)

# data[].attributes.body
teams channel for km/file sharing

intra dept discussions for ideation of projs to improve work processes/reduction of manual work

# data[].attributes.headline
Sync up more on important workstreams throughout the year so that we can respond quickly on collaborations

# data[].attributes.subject
Sync up more on important workstreams throughout the year so that we can respond quickly on collaborations

# data[].attributes.body
This is to ensure Sensing’s work can contribute in meaningful, impactful and timely manner

# data[].attributes.body
There can be more opportunities for cross-sharing/learning of what each team is working on, since the structure of OPPD means that work is confined largely within the teams themselves

# data[].attributes.body
It will be great for sensing to have a deeper understanding of other team's work to come up with effective tech solutions

# data[].attributes.body
Theresa: more frequent sharing across teams to discover new potential areas for collaboration e.g. sharing of latest technologies/tools by sensing team so that we can potentially leverage on these new developments in our existing work

# data[].attributes.body
Team huddles are good but maybe we should meet together as one OPPD a bit more, to get a sense of how the other pieces are moving, without taking much more time. Then ppl can also ask questions that are unrelated to their daliy work and bring up cross-cutting items (if any).

# data[].attributes.body
Dept/teams have expanded in the past year, good because divide the heavy workload, downside is that it may be tough for everyone to know what is the latest update etc.

More communication within and between teams, collaboration on documents (can simultaneously work on the same document)

# data[].attributes.body
Would be nice if we have brownbags as a dept to do cross sharing of work pieces or learning points.

# data[].attributes.body
If teams are facing a complex problem, or issue which is unknown unknown, we can have a white board at OPPD to write them down and to tap on OPPD's collective wisdom for ideas and solutions or to testbed ideas :)