We often do need multiple value propositions. A stakeholder/feature table is a great way to capture relevant stakeholders, their interests in features/outcomes, and an overall picture of value of the system being conceptualized.
In #MBSE, the clarity we need is not in the diagrams. Whether dealing with humans or software, the meaning is in the metamodel. https://t.co/KHtcXV63oy
@Vendbridge Agreed - "listen to music" has been a job for hundreds of years with many solutions ranging from orchestras, radios, record players, to portable music devices.
In #MBSE, the clarity we need is not in the diagrams. Whether dealing with humans or software, the meaning is in the metamodel. https://t.co/KHtcXV63oy
@renebastijans@alanklement I found WC&KC to be kind of fluffy, unactionable, and philosophical gymnastics. I'm good with the Ulwick/JTBD/ODI approaches. BTW I'm #BBAK so I don't think he cares what I think. Also BTW you must research or publish in the systems area, yes?
Let's say I'm on a team designing a $1M complex industrial machine. Do I start with 'switch interviews' ?? They may be fine for some cases but not this one.
@renebastijans This 'ought to be' and new-me are unnecessary philosophical gymnastics, the Ulwick JTBD/ODI approaches cover all situations very nicely and in complex electro/mechanical/software systems.
@renebastijans Agreed, those are all called stakeholders, an integral part of a systems model. Let's go beyond systems thinking to systems modeling and MBSE, check the other posts here.
@renebastijans It might be a short interview to ask the factory manager about progress/change/new-me. Jobs are functional, especially this one, and the Ulwick JTBD/ODI approach seems ideally suited to it and many others.
If you're a designer embarking on a design project, how do you know what types of basic information you need to collect/develop and how much of it. Not techniques like personas, switch, job maps or whatever - types of information. SE metamodels help answer these Qs.
The core functional jobs are closely aligned with systems meta-model concepts of modes, common operating conditions of a system, and a very useful concept for identifying/grouping important interactions and outcomes. https://t.co/idCRLZCP4H
Core functional jobs and associated outcomes are (by definition) solution agnostic. Consumption chain jobs and outcomes are sometimes solution dependent. One goal of innovation is to eliminate or automate consumption jobs. Learn more:
https://t.co/dux7M2VT9m
#JTBD#JobsToBeDone
Is 'cut wood' a #JTBD ? Yes, absolutely - humans have found it important for thousands of years and developed hundreds of solutions for it from axe, saw, to laser cutting. https://t.co/im1uMXdp1W
If people buy products to get a job done and people buy products to perform tasks (like hang a picture or cut wood in a straight line), then tasks (or anything people buy products for) must be jobs. Simple logic.
#JTBD Theory: core tenets https://t.co/46qmd6jzRy
#JobsToBeDone
So how to 'Be Goals' work if developing a machine for a factory?? The plant manager, purchasing manager, and machine operators don't own it and have no interest in it as part of an 'ideal self'. #JTBD
@mikeboysen@daughterofbev@jmspool@stoneykun@vikingux So @mikeboysen - do you draw a distinction between the job of the farm itself (grow or provide a crop) and the tractor which seems to perform several steps in the job map (prepare the field, fertilize the crop, etc.).