Half a croissant, on a plate, with a sign in front of it saying '50c'
h a l f b a k e r y
The leaning tower of Piezo

idea: add, search, annotate, link, view, overview, recent, by name, random

meta: news, help, about, links, report a problem

account: browse anonymously, or get an account and write.



Ways of Approach

How to think about a particular subject or task, in three paragraphs
  [vote for,

There's lots of things people try, that is outside of their day to day line of activity, because they need to do this thing just once. The equilibrium between investing a lot of time learning how to do it all, gaining experience and then performing this one-off task, versus paying someone with expertise to perform it, results in neither direction being adopted. The decision instead is usually to “have a go” yourself, and accept what you come up with.

What might be nice is to encapsulate the “way of thinking” that is at the core of carrying out all of these various lines of expertise. What might be nicer is that instead of a full-on course or module of education, it could be summed up in three paragraphs (or 144 characters) (to annoy the twitter).

The ways of approach would hardly mention the core topic at all, hardly mention any of the paraphanelia or features, hardly mention the subject at all. Instead it would encapsulate what is trying to be achieved throughout, as a way of thinking.

It's difficult to explain. I need one, for this.

Ian Tindale, Mar 18 2016

Stadard Engineering Design Methodology model http://www.nasa.gov...edc_flow_k4_540.jpg
[LimpNotes, Mar 20 2016]

OODA Loop https://en.wikipedia.org/wiki/OODA_loop
[LimpNotes, Mar 20 2016]


       Sounds like you've had one or two or six already.
Voice, Mar 18 2016

       Eh? No?
Ian Tindale, Mar 18 2016

       If you had to explain something you’re very good at, very practiced at, and thoroughly familiar with, to someone who is completely new to it, you might well start with a few introductory technique or mechanism explanations, depending how good you are at explaining things. Or you might start with a sequence of instructions — do this, when that happens, do that, then when this is done, do those, then stand back and do this while that occurs. There’s many ways of explaining how to do a thing.   

       What this is, is not explaining how to do a thing. It doesn’t have anything about the steps, the techniques, the widgets or the processes. They’re not mentioned, or at least, not the main focus.   

       What this is is an encapsulation of the directive or objective thought process in the minds of the experienced. What matters, or what is important, or what do I want to see at the end, or when I see it, what constitutes success in that result, or what constitutes the whole point of doing any of this. It’s probably more the why, but not really expressed as a why.   

       It could be in the form of parable, or analogy, but it doesn’t mean that it always is. I’m trying to think of an example or two. It’s the strategy, not the technique. Teach that up front, I say.
Ian Tindale, Mar 18 2016

       So I think I sort of get this. It reminds me of the difference between two kinds of recipes. One is very specific and doesn't explain why you're whipping the cream for exactly 6.5 minutes with a certain kind of wisk. The other is looser and assumes baseline knowledge or common sense and also explains the reasons or desired outcomes of certain steps. Whip until you see stiff peaks. Or something.
the porpoise, Mar 18 2016

       Keep going.
Ian Tindale, Mar 18 2016

       Oh yes, and another thing. Why I thought of this. It was imagining there was a resource for people who have to do a thing, but haven’t done it before, and probably won’t take it up as an occupation and do much of it in the future. It’s an encapsulation of the way an expert would think as opposed to the way a beginner would think, about the whole thing.   

       For example, sometimes a person programming an app has to every now and then make a promotional ad or video or poster. That might not be their expertise at all, so they might think that doing such a thing goes this particular way, with all these ingredients. Whereas an expert would throw all of that out and what they’ve done with it and say “try this instead”, and the newbie smiles broadly as if in revelation. The difference is encapsulated in this little “way of approach” which could be availed to all when needed. There could be “ways of approach” ing all sorts of topics or activities, which would save a lot of hassle and cut down on a lot of unsightly embarrassing unprofessionalism cluttering up the world as it is.
Ian Tindale, Mar 18 2016

       But for most things, isn't this approach just to go and look at a few relevant YouTube videos or an iFixit guide out something?
hippo, Mar 18 2016

       Baked. "Use the force, Luke."
MaxwellBuchanan, Mar 18 2016

       Whenever I have had to tackle something I have no experience in, (take-your-pick), or have had to walk someone else through tackling something new, I've found it most helpful to start off with what 'not' to do first.   

       It's far more important to know the pit-falls in advance than it is to be bombarded by all of the finer details or tricks-of-the-trade.   

       People who would value this would also be much more inclined to go with one of the first 2 methods: get good at it first or get someone else to do it.   

       Donald Trump, for example, has no foreign policy experience yet is his own foreign policy advisor. I suspect this is not because he does not know where to get expert advice, but because he places little value on expert advice.
bungston, Mar 18 2016

       NASA has the Standard Design Engineering Methodology which is something like what you are asking for but necessarily tailored to engineering projects. Also comes to mind, the OODA loop model proposed by military strategist John Boyd. <links>
LimpNotes, Mar 20 2016

       // It's difficult to explain. // [marked-for-tagline]
whatrock, Mar 20 2016

       Yes, I recognise this - in software development, there's a whole bunch o'frameworks out there that presuppose you've been doing things a particular way, and try to solve niche problems associated with those behaviours and methodologies. So Django, or Hibernate, or Beans, or anything that includes the word "Enterprise" presupposes that nobody knows what a database is or how to use it properly - and then there's all the build tools like Maven or Ant, which makes other assumptions about where barriers to delivery lie.   

       So with all these things, yes, there's a context that's often assumed, glossed over or otherwise ignored, but which is at the root of the particular tool, method or process under consideration.   

       Expressly communicating this problem context may provide people with an appropriate orientation or "way of approach" they need to quickly assimilate the new information.
zen_tom, Mar 22 2016

       Sounds like Nash's Game Theory as applied to differing ways to approach any unique situation.   

       Personally, just pay the man.
RayfordSteele, Mar 22 2016

       So, like when I coached 11-year-olds how to do a soccer throw-in. It didn't matter if it was a miraculous throw, just put the ball in play without it being called a foul throw like the last seventeen times. In a row.   

       1. Keep your feet together. The most common throw-in foul is lifting the back foot. 2. Touch the ball to the back of your neck. The ball must be delivered from behind the head. 3. Throw it hard. The ball must be released over the head. A softly thrown ball looks like a foul throw anyway.   

       There should be a unique name that can be searched for, like "howto". A portmanteau of quick, zeitgeist, haiku, etc.
xrayTed, Mar 22 2016

       If this idea is an attempt to demonstrate this idea, I'd say it doesn't recommend itself very well.
notexactly, Mar 30 2016

       Rules of thumb?
tatterdemalion, Mar 30 2016

       [tatter] reminds me of a book, "Rules of Thumb" by prominent Anglo-Serbian author Hugh Ristic, I think it's out of print now.
zen_tom, Mar 31 2016


back: main index

business  computer  culture  fashion  food  halfbakery  home  other  product  public  science  sport  vehicle