Skip to main content

最有效的解决问题的方式

领导者通过问题看到机遇

领导者看问题不是作为干扰, 而是不断改进和看到原来没有意思到的机会
A leader must never view a problem as a distraction, but rather as a strategic enabler for continuous improvement and opportunities previously unseen.

responding promptly and efficiently  with a comprehensive step-by-step incident report that included our change management efforts.


Effective leaders connect the dots and map-out a realistic plan of action in advance. They have a strategy that serves as the foundation for how the problem will be approached and managed. They anticipate the unexpected and utilize the strengths of their people to assure the strategy leads to a sustainable solution.
Never shoot from the hip when problem solving. Avoid guessing. Take enough time to step back and assess the situation and the opportunities that each problem represents. Make the problem solving process more efficient by recognizing that each problem has its own nuances that may require a distinct strategy towards a viable resolution.


They never realize that, in the end, all problems are the same – just packaged differently.


silo mentality is a reluctance to share information with employees of different divisions in the same company. This attitude is seen as reducing the organization's efficiency and, at worst, contributing to a damaged corporate culture.Jun 25, 2019



https://www.forbes.com/sites/glennllopis/2013/11/04/the-4-most-effective-ways-leaders-solve-problems/#348d59cd4f97

  • Generous favors blossom into friendships.
  • Odd jobs blossom into annual contracts.
  • Coworkers blossom into supporters.
  • Bosses blossom into advocates.
  • Friends blossom into partners.
  • Ideas blossom into enterprises.

Comments

Popular posts from this blog

for loop in javascript - promise - .eslintrc for "for of"

the vast majority of cases  map ,  forEach ,  find  etc. can be used.  async function printFiles () { const files = await getFilePaths(); await Promise.all(files. map (async (file) => { const contents = await fs.readFile(file, 'utf8') console.log(contents) })); } const inventory = [ { name : 'apples' , quantity : 2 } , { name : 'bananas' , quantity : 0 } , { name : 'cherries' , quantity : 5 } ] ; const result = inventory . find ( ( { name } ) => name === 'cherries' ) ;   function getFirstMatching(array) { for (let item of array) { const result = heavyTransform(item); if (result) { return result; } } } Specifically this shuts down the whole no-restricted-syntax. If you want to cherry-pick, here is the current definition: 'no-restricted-syntax' : [ 'error' , { selector : 'ForInStatement' , message...

Apollo client - cache APIs - auto update cache - erase cache - reactive variables - deletion - addition

Apollo Client 3  Local only fields Reactive Variables const cache = new InMemoryCache ( { typePolicies : { Todo : { // If one of the keyFields is an object with fields of its own, you can // include those nested keyFields by using a nested array of strings: keyFields : [ "date" , "user" , [ "email" ] ] , } } , } ) ; This internal data is intended to be easily  JSON-serializable , so you can take a snapshot with  cache.extract() , save it somewhere, and later restore with  cache.restore(snapshot) . Here’s a mutation called  EditTodo  that returns the new  todo  value in the mutation response. mutation EditTodo ( $id : Int ! , $text : String ! ) { editTodo ( id : $id , text : $text ) { success todo { # <- Returning it here id text completed } error { ... on TodoNotFoundError { message } ... on TodoValidationE...

window.URL.createObjectURL is not (yet) available in jest-dom - testing scenario

Since  window.URL.createObjectURL  is not (yet) available in jest-dom, you need to provide a mock implementation for it. Don't forget to reset the mock implementation after each test. describe ( "your test suite" , () => { window . URL . createObjectURL = jest . fn (); afterEach (() => { window . URL . createObjectURL . mockReset (); }); it ( "your test case" , () => { expect ( true ). toBeTruthy (); }); });