A conept is an implicit handover of responsibility, analysis and implementation.
Whenever someone is asked to create a conept for a vague idea.
What is actually meant is to implicitly handover any
hard decisions (functional and technical) from the asking party to the employee that
will be creating the conept.
For the requesting party, a finished conept is to be considered as the fruit of all powerpoints presented to upper management, leading up to the point of the delegation of the creation of the conept.
After a demo of a conept, the conept
will then be functionally reverse engineered so that it looks like that the initial requirements had always been describing exactly what the conept does up until that point.
Whenever that happens, the conept
will be used to extrapolate a roadmap for
future similar conepts for the
next 10 years with
hard-limits on estimated mandays.
We're trusting you to create a conept for the roadmap we've described for this product. (phrase
used publicly)
Thanks to the conept, we've now figured out what we
actually meant with this '
technical uplift'. (phrase not used publicly)
