EIR Review Process
One key to dveloplent performance is ongoing review for organizational learning.
Review can take many forms.
- Cardinal rule: as soon as something is published, it can be reviewed. Review is not possible without going public in some form. The most effective is documents and media - such that many people can view at zero cost. Thus the need for a transparent, open source process.
- Cardinal rule 2: publish early and often, especially when the work is not finished. You can publish intent, and get feedback even on intent. Nothing is ever complete as persistent change is a feature of all systems. Waiting till something is done means that it will never get published, and is a common pitfall for ordinary mortals. To become immortal - publish.
- A venue for pictures must be created, so visual review of pictures is possible in a transparent fashion.
- Data Cole tion should be ongoing. A data collection form should be used virtually, and paper documentation can be taken as well. Both complement each other, and either should not be done exclusively.
- Plans should be published for formal and informal review. FB, blog, Linked In groups can be a great source of review. For this to work, content should be published in a reviewable format.
- An executive summary is reviewable, and should be published. Further, it should be published on an ongoing basis as changes and lead jngs happen.
- Protocols, procedures, and processes can be defined and are reviewable.
- Arguably the single most important point for review for Distributive Enterprise creation is identifying key advisors that can help in development. This can build years of experience into the development, and retired SMEs may be a good target audience for such review.
- A business plan is reviewable as long as it has clarity and sufficient t information for review. Revenue projections, workflows, ergonomics and time requirements, process improvements, marketing strategies, execution details, tech ology reviews, and many other elements if a business plan can be reviewed. The key is detailed analysis of each element, such that a business plan is backed up by a study of Industry Standards, market research, and other studies.
- SME DE webinars can be leveraged by requesting time from leaders i n the field.
- SMEs can be solicited deliberately for feedback
- An advisory team should be created from top SMEs .
- Weekly review should explore SWOT analysis, and address weaknesses by tapping strengths
- Effective means of communication should be developed to facilitate digestibility of content that is up for review.
- A formal review meeting via the internet should be organized on a regular basis, such as quarterly.
- A log should facilitate review by communicating effort, which is reviewable for time and priority allocation.
- Blog posts can update on progress, and solicit feedback. Active distribution to potential reviewers can help this.
- Monthly review can include a specific list of key issues to explore, so atemplate for monthly project review should be drawn up.
- Diagrams, summary sheets, info graphics, and other digestible assets are a great way to solicit feedback, as well as to recruit further assistance.
- Active promotion of the Distributive utive concept can be a way for others to test the Enterprise in parallel. If our review team is solid enough, there may easily be others who can take on the Enterprise development in parallel. This requires detailed analysis and clear, high value proposition.
- Lean review can be critical to identify type 1 and 2 waste, and optimize the operation.
- rigorous detailed analysis of workflow and process based on known procedures can yield good data on cost (effort, time, resources).
- Spaghetti diagrams can be used to assess workflow organization.
- Good tool organization and location can facilitate efficiency.
- Dedicated review Sprints can be organized by inviting leading pra titioners to the virtual table.
- Webinar publishing can help to produce feedback who watch the webinar at a later time.
- Rapid prototyping of workflow can be obtained by planning out processing and measuring time taken in a simulated workflow.