Create a component/process outline the reaction and measurement device/process, and pre-seed the discussion forum with topics corresponding to the major elements of the outline. This creates focus for people to add ideas, suggestions, critiques, comments, etc.

Hi Jim,

We are intending to do this and think it is great that you have suggested it too, makes us feel a little more part of a team with suggestions such as this.

We are well on the way to designing our second generation reactors and will seek collaboration and input from anyone that cares to think through the many issues. We have discussed this a number of times within the facilitators and feel that there are many brilliant minds out there that could suggest that key ingredient / process / direction etc that would help us make our efforts all that more successful.

This is for by the people, for the people.

Please keep thinking and thanks for joining us on this journey.

B

Have you actually got the fuel wire yet from Celani? Have you actually found a way to start the LENR process?

Hi There

We are at the cell structural and thermal long term testing.

All will be revealed as it happens in the blog.

B

Thanks for your comments, Bob.

By coincidence (I swear! , on the same day that MFMP was announced, I started a Group at LENR Connect with the same basic goal.

lenrconnect.com/group/replication-cookbook (Replication Cookbook)

There's no question in my mind that, between the two, MFPM is now the better place to apply available attention and energy. Effectively everything at Replication Cookbook has been superceded by MFPM, which I think is great! The developments from HUGLabs are stunning.

Having said that, perhaps some of the structures that I used in the Replication Cookbook site might be beneficial to MFPM.

Those structures are based on methods I have applied in hundreds of collaborative process development facilitations on technical (IT) engineering projects. One of the key ideas from those methods is that if the problem is broken down into smaller elements, following objective functional break points, then it is much easier for the participants to contribute "evaluations" (goals, issues, change ideas, notes). My experience is that the combination of objective structure and focused subjective brainstorming can significantly accelerate collaborative development.

Another idea is to have those focused topic discussions matched with more static pages that accumulate the major points of agreement (agreement which can be explicitly asked for if it is not obviously represented in the discussion itself). That way people can get a summary and jump into the conversation without having to read all the discussion threads. This works because the topic is a focused area in the overall outline to begin with. Someone has to maintain the cumulative page, however, that's payoff is more progress, because...

The critical resources in collaborate development are the participants' ideas, judgments and impulses to contribute. If so, method and structure should be designed to best serve and leverage those.

If this approach is of interest, the starting point is to develop the component/functional outline. And the way to do that would be (following the method) to set up a focused discussion and a cumulative page for the topic outline development. If such a discussion is set up, I'll be happy to add ideas to it.

And having said all THAT, it may be that HUGLab has got the whole business of reactor components and process so far advanced that detailed collaborative development in those areas isn't going to be that productive. On the other hand, such an outline/discussion structure might be useful for education and simplification. If so, the detailed part-by-part photo approach I tried on the Replication Cookbook site (lenrconnect.com/group/replication-cookbook) might be useful for that.

We are very keen for support in any practical way. Thank you for your offer - One of the team will look at your considered thinking and we would love to have you on board.

We are using Survey Monkey to guide some development. We intend to use this extensively to take votes on aggregated information. One way you, or a member of your team could really help right now, would be to aggregate information offered up in these blogs and send us a summary on a periodic basis. whilst there is only a few 10s of peoples ideas - it is manageable - but given the significance of this endeavour we hope we will see information supplied my many 10,000s of people. at this stage, the kind of structured model you suggest with guided and summarised threads would really help our progress.

We would be grateful if you could work within your group to assign individuals to forum threads and parse the information in this way. With a working group - we could extract ideas for vote assessment and others for other types of analysis.

When we start publishing our blog on the second generation reactor, we hope people will engage in suggesting design improvements and component suppliers etc. We are moving extremely fast though, so people will really have to keep reading this forum and our various activity blogs as they emerge or they will loose track of us!

B