The Keirsey Temperament Sorter (KTS) is an assessment designed by David Keirsey consisting of 70 questions/choices, each with 2 possible answers/decisions. It is designed to categorize and help to better understand the subject's personality and temperament. It was first presented in Keirsey's book Please Understand Me. It exploded in popularity, and has been adopted worldwide for many different use cases.
It is influenced by the Myers–Briggs Type Indicator (MBTI), and according to Keirsey, it is meant to address some issues/flaws that were present in Myers' approach. Myers primarily focused on how people think and feel, whereas Keirsey focused more on behavior, which is directly observable.
In the original format provided by Keirsey, the subject may find it very difficult to answer some of the questions because they feel closely or evenly aligned with both available answers, but they can only choose one or the other. This can cause a "randomization" effect and possibly result in an inaccurate assessment of the subject's temperament.
For example, say the subject answers 10 of the 70 questions randomly because they felt 50/50 about the answers for those particular questions. This may lead to the subject believing their temperament is of one type when it is actually of a different type, or perhaps an evenly mixed type.
Just from those 10 randomly-answered questions, each having 2 possible answers, the subject would have over 1,000 different combinations of possible results, potentially making it difficult to know for sure what their primary temperament type is.
The goal of this application is to address the fine lines between temperament types, as well as the "mixed" types referred to in Keirsey's book.
The application will offer the original assessment designed by David Keirsey in its original format, as well as one or more additional formats. The additional format(s) will allow the user to answer each question on the assessment in a less binary way, and present the final temperament result as percentages of each type rather than simply the nearest match.
This way, the user will not be forced to choose between 2 answers that they closely or equally align with, resulting in a more accurate assessment, and they will also see how closely they align with all temperament types, resulting in a more comprehensive understanding.
Possible non-binary formats (sorted from simplest to most complex) may include:
- The ability to choose both answers for each question
- A scale for the user to rate how strongly they feel aligned with each answer
- More than 2 possible answers for each question
Results will be presented textually and visually in the following format:
- The user's primary temperament type(s)
- Percentages of how closely the user is aligned with each type
The application is planned to include the following features:
- MVP:
- KTS in original format
- KTS in "enhanced" format(s)
- Users can take assessments either as a guest or as a registered user
- Users can have their results emailed to them or downloaded as a file
- Future Features:
- Users can share the site via hyperlink/email/social media
- Users can share their results via hyperlink/email/social media/file
- Users can invite others to take an assessment via hyperlink/email/social media
- Registered users can view/retrieve/share/delete their previous results
- Registered users can have "shared" assessments where the results may be visible to multiple users/parties
- Registered users can create "groups" where results from each group member's assessments can be viewed by other group members
- Companies/organizations can create an account to:
- administer assessments to candidates/applicants/employees/members
- view and manage assessment results within their company/organization
- manage members and permissions within their company/organization
- Ads, donations, and/or premium features to cover server upkeep costs and support development
- Possibly other assessments in addition to KTS
- Possibly mobile app for iOS/Android
- Front-End: React App (may be migrated to Angular later)
- Back-End: Spring Boot Microservices
- DevOps: AWS
- Database: DynamoDB (may be migrated to RDS later)
- SMTP: Mailgun (or similar API service)
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify