-
Couldn't load subscription status.
- Fork 202
[Pattern Draft] Hive Mind #579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing this @mishari.
Looks like a great start already.
A couple of ideas that the pattern might benefit from:
- can you explain the term "hive mind" somewhere? maybe best in the Solution section?
- possible rewrite the Solution section in full prose, rather than just bullets. This is the section that should contain the most meat, as many readers will skip from Problem straight to Solution.
- are you aware of any literature that we could reference in this field?
A purely technical comment:
I suggest to rename the file to hive-mind.md. The term pattern should not appear in the file name (as all of the files in these folders are patterns.
As this is an Initial pattern, I would be happy to merge this relatively quickly, to then motivate further input from other people in the community.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How to cultivate this? Any specific things that one can do to work towards this?
One other more general thought about this pattern:
is this issue something that you want to solve on the organization level (e.g. submitting entirely new product ideas), or on the team/repo level (e.g. submitting new feature ideas that may not be fully thought out).
The pattern currently uses examples that seem to stem from both of these areas, it seems?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's good, when possible, to express forces in terms of trade-offs; they are constraints that make the problem more challenging; trade-offs are possible at a cost. E.g., Inertia: employees often follow established cultural norms. Breaking the cultural norms and establishing new norms is difficult because of the same inertia.
This force isn't acting only on the employees who might have ideas to contribute, there is also the lever in the dimension of the force to change the norms.
I mention this because often with patterns, the solution involves expending effort/energy to use the levers to counteract the forces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could add these instructions to our template. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mishari your current version express forces in terms of trade-offs really clearly!
Is that something that you got ChatGPT to do, or did you write that on your own?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, after reading the forces again, I wonder if this is what @NewMexicoKid had in mind?
I thought that he meant trade-offs between two things that both have their benefits, so one must strike a balance that is right for the org, in order to address the specific problem.
The current Forces read more like <the bad thing> vs <the good thing>, so in that case it is clear that one would want to work more towards the good thing :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@spier, you're correct; however, even in the case where you have a "bad thing" vs a "good thing", the concept of the trade-off is important because you might not be able to attain the "good thing" except through a high cost (which may or may not be worthwhile). Further, because you're dealing with an assemblage of forces, moving the lever on one force could have unintended effects on the other forces.
The important bottom line is that the listing of forces should help the person who is thinking of using the pattern make adjustments to the proposed solution to fit their own context. E.g., the prospective pattern adopter may have a slightly different context or a slightly different set of forces. Seeing clearly which forces were present for the proposed solution in the pattern really can help them with adopting/adjusting this solution for a slightly different situation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, these are really helpful points.
As the Forces are one of the areas that I (and many others) are struggling with, I keep wondering how we might integrate some of this information into our template.
I could actually take your text above and integrate it "as is", and then see if it helps future pattern authors. That would be an easy test. Although getting feedback would take time, as brand new patterns are not submitted all that frequently.
I've made a lot of edits, not entirely happy with it yet but have committed it as a WIP for further feedback. Thank you @spier and @NewMexicoKid for your input.
"Celebrate WIP" could be another title for this pattern.
One thing that I found interesting: started reading the new Solution section and immediately thought "this sounds like ChatGPT". Then I saw that it indeed was. So apparently it does have some recognizable traits?
Curious what you asked ChatGPT to get this output?
@spier I started out with this prompt:
I'm writing an InnerSource Pattern called Hive Mind to motivate people in an org to "ask for help" Often in corporations, there's a strong need to release a finished idea into the open. But here in the InnerSource Commons, even a vague intuition can be expressed, with others in the community contributing to help make it whole, or discrediting it.
When implementing InnerSource or even open source, one should be encouraged to open up early on to elicit feedback from other participants in the community, treating the community as a "hive mind".
On a single-repo-level, here some things I can think of (but not sure if that is what you are after):
- creating an issue on a repo, describing an idea for how to fix a problem or implement a feature (without a strong attachment to an exact implementation, and also without a commitment to actually do it i.e. just exploring what is possible)
- opening a PR with the bare minimum to be needed to explain an idea (sometimes it is easier to show what you mean in code than in text (i.e. the PR has unfinished tests, missing docs, etc)
also a key message is instead of looking for ways forward by themselves, practitioners should just ask their respective communities for suggestions on how to move forward.
It seems in many organizations the culture is to solve a problem by yourself, or in a team, but not so much to do so in the open, bringing in participants and interested parties from far and wide.
the pattern will solve this problem.
Ask me questions you need to help me write the pattern, I will then ask you to generate it one section at a time
Then I refined the draft by commenting it and telling it to add text. Finally I asked it to rewrite the Solution as prose.
"Celebrate WIP" could be another title for this pattern.
I want this to develop into more cases where it's useful to reach out early. I think there are other cases such as "seeking help early" that also work and should be incorporated, which is why I used the "hive mind" using others as an extension of your mind I think really works as an analogy, therefore the hive mind title.
I will rewrite to add this aspect as well
Quick technical note:
I don't know why the gitbook-generation GitHub Action runs are failing on this branch. Looks like I might have introduced some issue on the main branch that somehow is impacting the GHA runs here. I cannot quite explain this yet.
Sorry about this hiccup. Will look for a way to fix this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job on this @mishari!
I think as an Initial pattern we can merge this pretty soon. Would be great to see if any org has implemented something similar.
I left specific comments inline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can let AI create an image illustrating "Hive Mind" for us?
"hive" is where the bees live, right?
Could imagine quite a number of cool illustrations related to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this pattern related to establishing a more positive "failure culture?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would be an example of a specific implementation of this?
Maybe this point could link to the "praise participants" pattern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate on what this block adds on top of what the "Create a safe space " section already contains?
The "brevity" bit seems new here. Also the idea sharing sessions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's interesting. Now that this is all in prose I am looking for highlighted phrases or a summary of the key points. In a way something similar to the bullet opoints that you had here previously :)
I think we could do this by adding sub-headings ahead of the paragraphs, or similar (I will add one example below, so that you get the idea).
For reference, these were the bullets you you previously had in this Solution seciton.
Previously the solution section bullets were:
- Create a safe space (like a specific repo, brainstorming channel) where employees can share unfinished ideas.
- Encourage opening (WIP or draft) PRs that are not fully complete but provide a starting point for discussion.
- Cultivate a community culture that values and rewards collaboration and feedback.
- Host regular "idea-sharing" sessions where team members can present their initial thoughts and get feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides my proposals above, I wonder if we could make the language a bit simpler, to make it easier for our international audience to understand the text?
e.g. "emanating" is a word that I would not have know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar sub-headings could be introduced for the other paragraphs, to create a short summary of the key point of the sub-section.
Had to try the image generators now :)
Some Inputs I tried:
- A hive mind. many individual pieces working together to achieve something. May contain bees. It should not look like a superhero.
- many super cute bees that are collaborating, as if they had a shared brain. not comic style
The first ones were all superhero style. I tried to get versions without bees but it didn't work. This needs more work 🤣
_e8a6c4fd-3614-4006-a80f-a83d3f3ef7e7
_67760cc2-32d4-46a8-847c-c432827d8742
_167d302b-c57e-44a3-8af8-09f94d4910f5
_1db5fa5a-0a02-4b07-b797-fce4a50e3755
_bdea097d-efdd-428c-aa23-7fba461b9f2b
This might go into a more useful direction
many comic-style humans sitting in small with different shapes and sizes. all of these rooms are within a human head.
If this pattern is about "risk taking" as well, then there is an interesting quote in this story about Panasonic:
... newly established the Risk Taker Award to recognize those who had worked on technically difficult projects even if they resulted in failure.
Hey @mishari.
Sorry about all the notification noise that you must have received from this PR.
I have been testing something related to a GitHub Action that did not run correctly on this PR, hence all those last test commits that I did.
Hope you don't mind :)
@mishari @fioddor one general question about this pattern:
Is this something that you have seen in action somewhere during your consulting work, or how did this come about?
Also please see the open comments on the PR.
As this pattern is still in Initial state, let's decide together what is "good enough" for the time being, so that we can get it merged into the mainline.
And as always: Thank you for contributing and sharing your knowledge here!
@mishari @fioddor one general question about this pattern: Is this something that you have seen in action somewhere during your consulting work, or how did this come about?
Yes, I see it often in organizations that are Silo'd, when they communicate it's often highly filtered.
Also please see the open comments on the PR.
Noted
As this pattern is still in Initial state, let's decide together what is "good enough" for the time being, so that we can get it merged into the mainline.
I'll look into the comments and get back to you.
And as always: Thank you for contributing and sharing your knowledge here!
🎉
This reverts commit 275085f.
Uh oh!
There was an error while loading. Please reload this page.
Initial check in of Hive Mind pattern as discusses in issue #371
cc @spier