To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
Languages
Recent
Show all languages
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
.
Leo
Newton
Brights
Milds

Problem finding

From Wikipedia, the free encyclopedia

Problem finding means problem discovery. It is part of the larger problem process that includes problem shaping and problem solving. Problem finding requires intellectual vision and insight into what is missing. Problem finding plays a major role in application of creativity.[1]

Different terms have been used for problem finding in literature including problem discovery, problem formulation, problem identification, problem construction, and problem posing.[2]: 200  It has been studied in many fields. Mathematics and science prefer to the term problem posing.

YouTube Encyclopedic

  • 1/3
    Views:
    10 708
    5 601
    2 263
  • Kevin Systrom: Finding the Problem is the Hard Part
  • Problem Finding, Problem Solving - Sr. Lecturer Sara Beckman
  • The Problem Finding - Problem Solving Conundrum: Frank LaBanca at TEDxLitchfieldED

Transcription

Finding the solution to the problem is the hardest part. I always thought like, you're faced with these problems that people have, you assume that you know exactly what you're going to tackle, and the hard part is finding that algorithm. The hard part is scaling that solution. It turns out... thank you, Mike... that the hard part is actually finding the problem to solve. Solutions actually come pretty easily for the majority of problems. Not for every problem, but for the majority of problems. And in our case, what we did is when we sat down and we were deciding to work on Instagram, what we did was we wrote down the top five problems people have with mobile photos because we wanted to build a product that solved problems. We didn't want to just build a cool app to look for a problem that people had. We wanted to do it the other way around. So what we did was we listed out these five problems. And I remember the top three that we circled. Number 1 was that mobile photos don't look so great. We've all had that experience... you're seeing the sunset, you take a snapshot, and it looks washed out, you can barely see the sun, etcetera. And we were like, 'That's the major problem we want to solve.' Number 2 was that uploads on mobile phones take a really long time. So we were like, 'What could we do around that?' Well, maybe if we started the upload way before you're done even editing the photo's caption, and what if we sized down the photo just to fit perfectly on the screen but nothing else? And that's the small little problem and solution that it turns out really delights people because they press 'done' entering their caption, it's already been uploaded. The third problem was that we really wanted to allow you to share out to multiple services at once. We felt like, should you have to make the decision of taking a photo with a Facebook app, the Twitter app, so on and so on, or should you just take it in one place and distribute it to many places at once? Those top three problems allowed us to really hone in on what solution we wanted to build. And that's really what Instagram became. I also wanted to say that once you have those top problems that you want to solve, you need to verify that they're actually the ones that people have. And really the way to do that is get your product in front of people very quickly and test that hypothesis. I think too many people wait a long time... and I'm going to talk about this a little later. Too many people wait a long time to see whether or not what they're working on is actually the problem people are having. And the last point is that, really, you should not be afraid to have simple solutions to simple problems. Like I said early on, I think too many people believe you have to solve things in a really complicated way. And at the end of the day, if you delight people even a little bit with a simple solution, it turns out it goes very far. That first day when we had something like 20,000 new users, I was like, 'Clearly there was a need for this that hadn't been done before,' and I'm so glad we tackled those simple problems. There's something about... in the tech community, you always want to feel like you're working on the hardest problem in the world. It turns out that simple problem becomes very hard at scale. And that's what's really exciting. In a way, we often... in our entrepreneurship classes we hear about the Big Hairy Audacious Goal, like, 'What's the huge chunk you're trying to bite off and tackle?' And one thing that really struck me was that that Big Hairy Audacious Goal could be bringing that simple solution to something delightful to the masses. Yeah. And that, in itself, is a huge challenge.

Processes in problem finding

Basadur distinguished problem discovery and problem formulation; then later problem generation and problem conceptualization. Runco and Chand distinguish problem identification and problem definition.[3]: 205 

Scholars distinguish between well-defined and ill-defined problems. Briggs and Reinig defined a well-defined solution in terms of space solution space. Pretz, Naples, and Sternberg defined a well-defined problem as one for which the parts of the solution are closely related or clearly based on the information given. Problem finding applies to ill-defined problems.[3]: 201 

Abdulla-Alabbasi and Cramond reviewing the literature on problem finding conceptualize five processes of decreasing of ill-definedness and distinguish ideative and evaluative processes. The processes are discovery, formulation, construction, identification and definition. Problem discovery is an unconscious process which depends upon knowledge whereby an idea enters one's conscious awareness, problem formulation is the discovery of a goal; problem construction involves modifying a known problem or goal to another one; problem identification represents a problem that exists in reality but needs to be discovered (such as an unknown virus causing illness in patients); problem definition involves modifying a problem but in a mostly evaluative rather than ideative way.[3]: 209–211 

References

  1. ^ Runco, Mark A.; Nemiro, Jill (June 1994). "Problem finding, creativity, and giftedness". Roeper Review. 16 (4): 235–241. doi:10.1080/02783199409553588. ISSN 0278-3193.
  2. ^ Abdulla, Ahmed M.; Cramond, Bonnie (2018-12-01). "The Creative Problem Finding Hierarchy: A Suggested Model for Understanding Problem Finding". Creativity. Theories – Research - Applications. 5 (2): 197–229. doi:10.1515/ctra-2018-0019. ISSN 2354-0036.
  3. ^ a b c Abdulla, Ahmed M.; Cramond, Bonnie (2018-12-01). "The Creative Problem Finding Hierarchy: A Suggested Model for Understanding Problem Finding". Creativity. Theories – Research - Applications. 5 (2): 197–229. doi:10.1515/ctra-2018-0019. ISSN 2354-0036.

See also


This page was last edited on 5 November 2022, at 17:03
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.