Step 3: Make a Collaboratory Prediction

[#1]

Hello Collaboratory Scientists!

Welcome back to Collaboratory Month 🧬

The third step in the Collaboratory method is to make a Collaboratory prediction based on your question and hypothesis. (If you haven't already, formulate a question on the Step 1 post, and form a hypothesis on the Step 2 post).

In science, a prediction is what you expect to happen if your hypothesis is true. So, based on the Collaboratory hypothesis you've already created, you can predict the outcome of your experiment. Here's a page that explains the difference between a hypothesis and a prediction - they're very similar! 

Example: Perhaps, you want to test an experiment about whether having more meetings results in more efficient collaboration.

A good question to begin with might be: ”Does having more meetings result in a project being finished more quickly?"

A good hypothesis might be: If we decrease time spent meeting by 25%, the project will still be finished in the same time.

A good prediction might be: If my team reduces meetings by 25% (and uses that time instead for async work), then the project will be finished on the same timeline. 

---

We'll award the Collaboratory badge to all Community members who ask a Collaboratory question :) Keep an eye on the main Collaboratory post to discover next steps!  

[Marjorie]

Question: Does using a collaboration tool (Confluence) for requirements will reduce our meetings?

Hypothesis:  If we use Confluence to elicit our initial requirements we can reduce our meetings by 20%

Prediction: If my team reduces our meetings by 25%, then we can focus on delivering the product faster.

[Kishan Sharma]

Question - How do we create single source of truth for better collaboration with cross functional teams ?

Hypothesis - Considering the complexity of the project, select the right collaboration tool and create a dashboard in a shared space where cross-functional teams can visualize the work in progress, check status, set goals - deadlines and assign them to appropriate teams for actions. 

Prediction - If we create a central dashboard which is accessible to all cross functional teams then there will be improved collaboration where teams can visualize the priorities, build consensus on objectives, remove bottlenecks and execute tasks in order to make progress towards project goal.

[Kristján Geir Mathiesen]

Alright @Bridget , how about this:

Question: Will using gamification ensure updating of knowledge documents (KB articles) in a Wiki (Confluence)?

Hypothesis:  Use meaningful rewards system attached to some sort of Confluence gamification to increase validity of KB articles by 40%. 

Prediction: If we use gamification of some sort attached with meaningful rewards, our KB articles are 40% more likely to be kept up to date. (not everyone will participate despite of rewards)

:)

[Jimmy Seddon]

Question: Is it more efficient to use a time-boxed meeting cadence or asynchronous communication to keep team members informed about what everyone is working on?

Hypothesis: If we use slack for daily status updates, we will reduce the amount of time wasted while people get distracted by tangent conversations/questions that aren't relevant to the entire team as those questions can be discussed in threads.

Prediction: I believe that by using slack threads for daily status updates, we will allow everyone to remain more focused on the work they need to complete while providing the opportunity to collaborate when and where it is appropriate.

[Kavya S]

Question - How can we bring accountability for content that was created out of collaboration? 

Hypothesis - Irrespective of the number of collaborators, clear accountability ensures good content health and bolsters confidence in content accuracy

Prediction - If we use an RACI chart, identify and assign roles to the collaborators right at the beginning, the onus will be on the respective members to ensure the content is up to date

[said kouzibry]

Question : Does encouraging team members to present the new tools and techniques they use to the rest of the team bring more opportunity for collaboration ?

Hypothesis : If each person discovers a new tool or technique each week in a team of 5 people, in 4 weeks, we will have 5 team members with 20 skills each instead of 4 skills each, which will allow them to understand each other's work and help more efficiently, offering more opportunities for successful collaboration.

Prediction : If the team has homogenous skills, testing and debugging will be 50% more accurate and product quality and consistency will rise by 50% lowering risks of delays.

[Sharon Tan]

Question: Would making documentation/meeting notes more beautiful and functional encourage your team to collaborate on that page more?

Hypothesis: A page containing a balance of graphics, structure, engaging content, and purpose would encourage users to contribute to that page more than the same content without these elements. 

Prediction: If a plain Confluence page used by a team is updated or changed to be more aesthetically pleasing and more functional (or if two pages with identical content are formatted differently) then the more beautiful and functional page will receive more engagement (views, likes, comments). 

[Brant Schroeder]

Question: What is the best way to get these team members engaged and using the products to benefit the whole team?

Hypothesis: Working with their managers to ensure that proper expectations are set should help improve participation.  Positively encouraging and reminding the team members to participate and reinforcing good behavior through positive feedback should improve product use.

Prediction: Working with managers and positive encouragement and reinforcement should improve engagement of those not participating by 60%.

[javodev]

Question: How long does it take to demonstrate Confluence's effectiveness to CEOs? Any strategy?

Hypothesis: If we use Confluence as documentation, progress report and user manual repository, the PO can show it on virtual meetings. In about 4 to 6 months, CEOs will be amazed for the availability of the documents and the work done, deciding to invest in software.

Prediction: Presenting estimation charts and the effect the tools have had on the quality of the deliverables will increase the chance that CEOs will invest in certifications by the end of the 4th month by 60%.

[Suvradip Paul]

Question: Is it a good practice to take and circulate meeting notes during the meeting(as part of meeting) or is it a better approach to circulate after the meeting is over ? 

Hypothesis:  We can use Confluence and create a place holder before the meeting with the date and relevant agenda. Followed by, we can draft the meeting notes and action items in that template and assign action items tagging relevant people. Now if the agenda, meeting notes and action items are limited can be easily managed with in meeting duration then the confluence placeholder ca be published during the meeting else it should be done with in a short interval and preferably the same day. 

Prediction: We can buildup a good habit of capturing agenda, meeting notes and sharing action items using confluence and circulating the meeting notes depending on the meeting duration and utilising the meeting slot most effectively.

[Mirek]

Questions: What is the most productive time of a day and maybe there is even a specific day in a week to get most of a team meeting that would fully engage everyone?

Hypothesis: Using Confluence before the meeting might improve productivity on a meetings no matter which time of day or day it is.

Prediction: If we use Confluence every day to collaborate on the specific topic earlier offline, everyone would be joining the meeting more prepared and would be ready for good discussion no matter which part of the day or specific day itself it is. 

[Amanda Barber]

Question: Does time-boxing individuals' standup discussions to 1 minute provide more time for and aid in facilitating collaboration following the traditional mentions of work done, work to do and blockers?

Hypothesis: By limiting time for each individual response and providing more collaborative questions around the JIRA board and/or upcoming work, the standup will evolve into a more collaborative time.

Prediction: If we use Confluence to document our meetings, specs and work; in conjunction with our JIRA boards, we can limit our traditional standup comments and allow for more time for true collaboration where it's needed most.

[Svenja Lorenzen]

❓ Question: To what extent does using the comment function/inline-comment function on a page reduce communication/collusion in chats.

💭 Hypothesis: In teams that use the comment function/inline-comment function on a page, fewer Slack/Teams messages are written.

🔮 Prediction: A team that is regularly reminded to record their communication/questions in the form of comments/inline comments, will have fewer Teams/Slack messages sent.