The best I can do is a general problem solving scenario.
This covers mental and physical problems more than social
problems, but Instrumentation does address communication with both
people and technology, so I will first review the mechanics of
communication. Imperfect communication is a major source of
problems in modern global (and personal) relationships.
Finding associates that complement one's skill-set is a superlative general strategy. Cooperation and collaboration are powerful problem solving tools. Cooperation and collaboration require trust. Trust is dependent on due diligence. Due diligence can not be accomplished without common understanding of the issues involved. Common understanding requires clear communication.
Therefore ...
Clear communication is the basis for the
Instrumentation syntactic strategy.
It is very mechanical to minimize possible misunderstanding
between people who live on opposite sides of our fractious little
planet. There are only two rules and one reason to remember.
This is Truth, unless it is false. You really can't say
that about any other field of knowledge.
The only apparently 'gray areas' in mathematics involve things
that we are not capable of comprehending, things such as infinity.
Mathematics is always predictively certain when applied correctly
and rigorously. Humans are often certain but only incidentally
correct.
Math (my personal nickname for it) supports logic, scheduling,
accounting, cooking, etc. Any activity which involves the
manipulation of quantifiable entities or events is dependent upon
mathematics. Math is a lot more than just numbers.
Know thy assumptions. Test thy hypothesis. Prove thy theories.
All else is just drama.
This is a method used to expose the shape of reality. This shape has dimensions that include time, space, temperature, pressure, electromagnetic field strengths and many other quantifiable phenomenon.
Science is the source of factual information.
Dealing with the possibilities and consequences of reality.
This is where the rubber meets the road. If you are creating, improving or repairing anything that has a physical component (and a lot of things that don't) you are engaging in engineering. Proper design of an enduring solution is the province of Engineering (however, see also Philosophy below for aesthetic considerations).
Engineering is the art of balancing maximum performance upon the limitations of the materials involved.
No one knows everything. Bliss is not a useful problem solving
technique.
This is in the 'Peril' spot
because available information isn't always true. The integrity of
the researcher has no bearing on the applicability of the result
to your current problem.
Modern information sources (such as the internet) have made finding information physically trivial, but assuring factual certainty has become a more critical concern. A recent reputable book from the library may be harder to find, but it stands a much better chance of being correct. You can use the internet to obtain that book and have the best of both worlds.
You can't really tell what information will be useful until you
need it, so it is best to study everything that you can
understand. You don't need to know all the details of everything,
but you need to be able to tell what general fields of knowledge
are applicable to a given problem.
Why are you doing this (whatever it is)?
You can't truly solve any problem until you know what the ideal
solution will be. Understanding the intrinsic philosophical
background of the problems space is a requirement for holistic
solution design.
Philosophy is the study of intangible ideals. This is also a major input to finding the root cause of the problem. Being the cause of the problem (and not being able to admit it) is the worst case scenario.
Solving problems is easier when you really care about the
outcome. Artificially making yourself care is counter-productive
in the long run. A coherent Philosophy can help you decide
whether or not you should get involved with the problem in the
first place.
Not necessarily related to Study. This isn't a bad thing, Learning can happen at any time.
Any time anything goes right or wrong is an opportunity to learn.
A 'fool' is someone who repeats their mistakes. If you don't want
to be an ignorant fool you need to start learning.
Everyone is ignorant of something. It is better to ask a question
and reveal your ignorance than to remain silent and ignorant. If
you don't know something you are ignorant. The cure for ignorance
is learning. If you don't ask you are stupid. True stupidity is
incurable.
You only get to stop
gaining Experience once. In the meantime, make the best of
it.
You can't keep doing the same thing and expect anything to
change. In order to decide what to do next, you need to know
what's available. This should be a harbinger of both Study
and Learning.
Your brain needs it. Dream is the essence of Soft Focus.
This includes all unfocused thought, not just dreams while asleep. Some problems can only be understood when you stop staring directly at them.
Before dreaming can be a useful problem solving technique, you
have to truly understand all of the Hard Focus aspects of
the problem. Dream is never a substitute for Study
(or for having an applicable comprehensive Philosophy).
This design only shows positive terms. Negative terms would be
the opposite of each 'passive' term listed below. If the term is
'active', the negative form will invoke the function or be used to
capture the state or current Value.
Quick Fix
(no elements) |
Dream |
Experience | Both |
|
#00 - Problem Solving Lock-in this block of terms (unplug Command Mode to exit, even if the Terms aren't commands) |
#01 - removal |
#02 - replacement | #03 - manual intervention | |
Learning |
#04 - regression |
#05 - fix the test data |
#06 - augmentation | #07 - Secure the evidence |
Philosophy |
#08 - support hotline | #09 - document the problem |
#0A - emergency procedure |
#0B - notify the users |
Both | #0C - silence the alarm | #0D - visualize the scenario |
#0E - assess the impact | #0F - crisis management |
Study
|
Dream | Experience | Both | |
#10 - reading |
#11 - speculative fiction |
#12 - example problems |
#13 - case histories |
|
Learning | #14 - expert opinion |
#15 - popular opinion | #16 - past experience | #17 - mentoring |
Philosophy | #18 - categorization |
#19 - openness | #1A - similarity |
#1B - awareness |
Both | #1C - hierarchical |
#1D - relational |
#1E - serial |
#1F - classes |
TheoryEngineering |
Dream | Experience | Both | |
#20 - theory |
#21 - analogies |
#22 - anecdotal evidence |
#23 - scenarios | |
Learning | #24 - derivation |
#25 - extrapolation |
#26 - doctrine | #27 - expertise |
Philosophy | #28 - cohesiveness | #29 - |
#2A - lemmas | #2B - coherence |
Both | #2C - world view |
#2D - hypotheses | #2E - lore |
#2F - cosmology |
Collaboration
|
Dream | Experience | Both | |
#30 - open discussion |
#31 - brain storming | #32 - senior investigators |
#33 - team facilitator | |
Learning | #34 - involvement |
#35 - casual conversation |
#36 - war stories | #37 - familiarity |
Philosophy | #38 - team elan |
#39 - shared goals |
#3A - shared values | #3B - trust |
Both | #3C - mutual interests |
#3D - mutual respect |
#3E - diversity |
#3F - consensus |
Science(no elements) |
Dream |
Experience | Both |
|
#40 - observation |
#41 - hypothesis | #42 - method | #43 - model |
|
Learning |
#44 - neutrality |
#45 - frames of reference | #46 - trending |
#47 - interdependence |
Philosophy |
#48 - rigor |
#49 - universal relationships |
#4A - repeatability |
#4B - causality |
Both | #4C - law | #4D - truth | #4E - conformation | #4F - boundaries |
Experimentation
|
Dream | Experience | Both | |
#50 - metrics |
#51 - flexibility |
#52 - applicability | #53 - suitability |
|
Learning | #54 - capture raw data | #55 - problem solving exercises | #56 - representative environment |
#57 - coefficient of correlation |
Philosophy | #58 - representative population |
#59 - control of variables |
#5A - concise record keeping |
#5B - statistical significance |
Both | #5C - chi squared | #5D - Chebyshev |
#5E - Gaussian |
#5F - discovery |
EngineeringEngineering |
Dream | Experience | Both | |
#60 - data | #61 - variable | #62 - constant | #63 - result | |
Learning | #64 - parameters | #65 - local minimums | #66 - local maximums | #67 - failure conditions |
Philosophy | #68 - isolation |
#69 - efficiency |
#6A - rules of thumb |
#6B - optimization |
Both | #6C - controlled environment |
#6D - synergy | #6E - load limits |
#6F - boundary conditions |
LearningStudy |
Dream | Experience | Both | |
#70 - curiosity | #71 - interpolation |
#72 - pedantry | #73 - specialization |
|
Learning | #74 - aptitude |
#75 - internalization | #76 - practice |
#77 - compensation |
Philosophy | #78 - existential acknowledgment |
#79 - inference |
#7A - expedience |
#7B - comprehensiveness |
Both | #7C - expertise | #7D - prescience | #7E - evaluation |
#7F - competence |
Mathematics(no elements) |
Dream |
Experience | Both |
|
#80 - equivalence |
#81 - sequence |
#82 - series |
#83 - function | |
Learning |
#84 - Influence Maps |
#85 - differential |
#86 - associativity | #87 - tool box |
Philosophy |
#88 - Problem Definition | #89 - integral |
#8A - distribution | #8B - Pareto Analysis |
Both | #8C - optimal solution | #8D - algebra |
#8E - Gantt Charts |
#8F - algorithm |
CategorizationStudy |
Dream | Experience | Both | |
#90 - differentiation |
#91 - Career Skills |
#92 - opportunity | #93 - Time Management | |
Learning | #94 - Affinity Diagrams | #95 - definition of criterion |
#96 - Drill Down |
#97 - Stress Management |
Philosophy | #98 - Object Orientation |
#99 - binary |
#9A - customer impact |
#9B - I Ching |
Both | #9C - narrow the focus |
#9D - decision tree |
#9E - Paired Comparison |
#9F - reframing |
DesignEngineering |
Dream | Experience | Both | |
#A0 - balance |
#A1 - alternative corrective actions | #A2 - undesirable side effects | #A3 - past solutions |
|
Learning | #A4 - bottlenecks |
#A5 - emerging technologies | #A6 - case studies | #A7 - Force Field Analysis |
Philosophy | #A8 - potential severity of problem | #A9 - customization | #AA - frustration avoidance |
#AB - relentlessly improve operational performance |
Both | #AC - customers' needs | #AD - market forecasts |
#AE - peoples' perceptions | #AF - enable future growth |
PhilosophyStudy |
Dream | Experience | Both | |
#B0 - goal | #B1 - imagination | #B2 - responsibility | #B3 - costs |
|
Learning | #B4 - competitors | #B5 - visceral hunches | #B6 - defer judgment | #B7 - benefits |
Philosophy | #B8 - divergent and convergent thinking | #B9 - innovation | #BA - improve the best ideas generated | #BB - philosophy |
Both | #BC -aesthetic | #BD - have fun | #BE - positive thinking | #BF - harmony |
Baseline(no elements) |
Dream |
Experience | Both |
|
#C0 - Performance logs | #C1 - comprehensive metrics |
#C2 - customer complaints | #C3 - progress monitoring |
|
Learning |
#C4 - Flow Charts |
#C5 - Cause and Effect Diagrams |
#C6 - Systems Diagrams |
#C7 - total system map |
Philosophy |
#C8 - structured approach |
#C9 - component interactions |
#CA - gather assessment data |
#CB - coherent system image |
Both | #CC - concise methodology |
#CD - complete coverage |
#CE - operational confidence |
#CF - normal process limits |
ExperienceStudy |
Dream | Experience | Both | |
#D0 - bench marks |
#D1 - problem growth | #D2 - symptom interpretation |
#D3 - danger sense |
|
Learning | #D4 - multiple environments |
#D5 - limit discovery |
#D6 - historical perspective |
#D7 - omniscience |
Philosophy | #D8 - benefits |
#D9 - workable fixes |
#DA - win-win approach |
#DB - holistic solutions |
Both | #DC - objective affinity | #DD - personal vision |
#DE - intuition |
#DF - comprehend the mission |
Test Suite
|
Dream | Experience | Both | |
#E0 - test case |
#E1 -Random Input | #E2 - corner cases |
#E3 - boundary conditions |
|
Learning | #E4 - evaluate |
#E5 - assess goals |
#E6 - performance criteria |
#E7 - conformance |
Philosophy | #E8 - document normality |
#E9 - development support | #EA - critical coverage |
#EB - understand the environment |
Both | #EC - automated evaluation |
#ED - Impact Analysis |
#EE - Risk Analysis |
#EF - assure optimal operation |
Quality Assurance
|
Dream | Experience | Both | |
#F0 - failure rates |
#F1 - Action Plan |
#F2 - change management |
#F3 - measurable results | |
Learning | #F4 - modify specifications | #F5 - update training | #F6 - on-going controls | #F7 - monitor the long-term effects |
Philosophy | #F8 - potential causes | #F9 - review work flow | #FA - investigate variance |
#FB - improve practices and procedures |
Both | #FC - intervention |
#FD - intangible factors |
#FE - publicize solutions |
#FF - customer satisfaction |
Intelligence is not a single thing. Intelligence is a convenient
name for a collection of mental skills which are used to solve
(and sometimes cause) problems. It can be broken down into a near
infinite number of talents such as memory, mathematical ability,
pattern recognition, deductive and inductive reasoning (which are
themselves collective entities), etc.
Apparent intelligence varies according to the task at hand. Someone who appears brilliant in a classroom may look like a complete idiot on the street (believe me, I speak from personal experience).
Instrumentation is intended to organize
data so that it can be used more easily, but fluent use of
Instrumentation would only demonstrate facility in a few
individual skills. It would be highly premature to attempt to
predict the skills involved at this point in the development
process.
Instrumentation may augment some mental skills and degrade others
(I would be shocked if there was no effect at all), but guessing
in advance of hard performance data is a fools game. I hope that
Instrumentation will facilitate artificial intelligence, but that
won't help you until you have a computer in your head.