---
# System prepended metadata

title: SPLAT Feedback

---

[Julio] Some ideas:
- Keep track of team objectives and key results
- Improve our onboarding guide on key knowledge (prow, insights, topologies, operators, ...)
- Build a cross-team "i need help" process/tools
- Build a cross-team "who owns what" process/tools
- Build a cross-team command line tool
- Build a direct feedback loop with a few customer/partners.
- Build a way out of prow


[Marco] a few ideas:

- create some SPLAT/internal channel/queue for PR feedback/review (as a team first, before asking component owners): reviews are also a learning process (IMHO), this could help owner to learn (standards in the OCP group, code skills, identity areas to improve, action items, etc), and for reviewer is also an opportunity to share the knowledge.
- create some group(team, 2+) quartely [cool] goal: one of the best experiences (and I learned a lot) in SPLAT was working in a group with a goal (Alibaba onboarding, Install flex, OPCT, Oracle cloud, external, etc). Examples: build some project, present a session, write a blog post.