at highlevel, you must know what you're supposed to deliver, which can be extremely difficult when not everyone does (incl yourself) so people start to second guess things to 'get things moving' which can be a huge risk and potentially completely wrong.
Understand the actual problem , write it down and repeat back to get confirmation.
write down the (non)functional requirements from the stakeholders, the exact scope of work before doing anything, again repeat back to get confirmation,
In the murky world of greyness where people do not really know information or the full set of data, agree (again before starting work) on little subtasks/ plans to get the information (PoC)
Write down the Risks/ Assumptions/ Issues/ Dependences of your actions and again get them signed off
all this takes time and can be extremely boring relative to getting stuff done, so a lot of people just do stuff they think is right
I'm a divergent thinker and like to bounce ideas off other divergent thinkers, so I can work alone or with others, but/ ideally they need to be creative/ open
Once we have a list of ideas, then whittle the list down with the realist and pessimistic people of the group; until there's one obvious way forward or a couple of least worse ideas.
Generally most people are better at telling you what you can't do,
I was royally pissed off when I suspected my brand new Lenovo laptop was acting strange. The only in the end to stop it was to reinstall the OS, I then later found out it was the superfish issue
I look at Boardgamegeek almost ever time I make a purchase of a game and to get ideas. To see what other peoples think, their reviews about the game and game play, strategy vs luck element, type of game etc
It's similar to imdb for movies, its a place full of opinions. I take everything with pinch of salt, but it's the best review site around
each company is different,
from my experience it would depend on the severity of the fix, and the severity of the issue. the problem would get resolved by any means ie temporary sticky plaster if necessary.
Another team would then assess and analyse the root cause from a company wide perspective and then assess the risks, costs and impact and then make any modifications (possibly redoing the temporary fix, and fixing it properly)
Real issue, a call center main telephony system and one of the management servers kept crashing causing over 1400 call center people to stop working. Temporary fix was to re boot the servers every 4 hours causing minor pain, but the call staff was up and running.
After a whole stupid week of the engineers not being able to find the route cause it was escalated extremely high and our team was brought in and we found the root cause in seconds (literally)The servers was VMs and the engineers hadn't checked the physical ESX server they were hosted on. another VM on the box caused the server to go unstable (ESX not configured correctly).
BAU project set up to audit/ report and fix all the ESX servers in the company for other stupid config issues
I'm no where near an expert and I'm not a big fan of software patents,
on the subject of prior work, and just thinking out loud, but I wonder if USPTO could set up some rules whereby the person asking for a patent has to do some sort of search for prior art, in order to get the patent
and if they don't or do it badly/ not to the rules, then a penalty is applied, financial or immediate ban on patients?
I've just signed up to the equivalent in the uk called government gateway
you have to provide information and details from two of the following: Passport, last tax submission or driving licence
the sign up to the internet healthcare system used by my doctor seemed to be run by a 3rd party (not happy) needed general information and a picture of my passport or driving license. I declined, because it's a third party and I could not be bothered reading the large list of ways they will likely sell your data and partially because I don't need my doctors info online
explaining fairly complex stuff to non technical people and using diagrams (we called them crayon diagrams) can be an art form. Its a balancing act of showing something too complex vs too simple ie,showing one box and saying its broken(I've seen that happen).
imho, The best way to start is by asking the stakeholder what they know about the system and asking them stuff. this is good in different ways,
1) you can assess their level of technical abilities
2) assess how interested they really are
3)engage with them and create a personal relationship
and take it from there, using analogies can be extremely useful
at almost every place that I've worked at, it's been the task of the manager/ senior managers to keep the stake holders, general staff/ users at bay, to keep the techies happy and free of harassment during severity one incidents
and that includes making coffee, tea and bringing sandwiches/ pizzas
absolutely, I'm also guessing not many people did listen to these new format versions of these shows either.
the only time I've ever heard the Goon show or Hancock's Half Hour, has always been whilst listening to the radio (typically 2 or 4) that makes a reference to the shows and plays a few seconds clip
Within my limited field of family and friends I would say that people have heard about them, but have not really listened to them
I have made a couple of huge ones - luckily I kept my job