jessy.io

Open Collaboration Hardship Thoughts:

Internal Collaboration:

• Information flows everywhere (instant communication + documentation of institutional knowledge) within the team, everyone uses different apps and communication channels and in different in-person conversations, and important information are sometimes not captured and shared with everyone (e.g., less chance of being shared to team members who need to know about them, and lack of documentation can leave those who later join the projects confused, time wasted catching up, institutional knowledge lost once member leaves)
• How to turn the platform into one of the primary platforms used by the organizations so the platform doesn't become an information graveyard? In other words, what's the specific pain point of the direct user from the organization

External Collaboration:

• Fear of sharing resources due to others "stealing" the hard work when resources are scarce and competing for the same resources. Therefore, even if willing to share, only share “non-important” resources between organizations

• Sharing only “perfect” but not up-date resources/information due to the desire to show up as not a perfect and put-together organization in the eyes of exports (e.g., government, scientist, money-granters, etc.)

• Code is modular by nature and can be easily standardized. But other “soft” resources (e.g., company playbook, marketing material, HR process) are usually not able to be modularized/built upon very quickly - how to solve this? (Maybe focus on resources that can be modularized such as curricula)

• How to measure and quantify contributions and create a positive reinforcement cycle (proper reward mechanism)

• [ ] Finn Woelm

• [ ] Dr. Christian Busch - serendipity

• [ ] Bodo Hoenen - GPS for learning

• [ ] Alex Fiel

• [ ] Hilda Huang

• [ ] Kelli