Developers sometimes begin a project by racing to the specification document and an ERD. Wait! Even if you're developing iteratively, there's a huge amount of potential being missed in most projects.
I propose that your projects will be more successful and valuable to your clients if you think of yourself not just as a database developer but as a process consultant. This presentation outlines a few concepts for addressing the human and political aspects of database system development and concludes with an example scenario.
This was presented at a FileMaker training session and is my first public presentation. Thank you for looking!
For example, think about when you are evaluating your solution… how much to do you focus on usability and business impact as opposed to data integrity? (unless they bark at you)
David Kachel of Foundation Database Systems, “Are You Taking Notes?” in White Paper for FMP Novices, 12/5/2006, p. 57-60.
Intuitive structure represents their mental model
Cf Don Levan, Psychology of Effective FileMaker Pro Solution Design in FileMaker Advisor
Understandable solutions are good, but great solutions cultivate higher understanding as well.
Understandable solutions are good, but great solutions cultivate higher understanding as well.
Understandable solutions are good, but great solutions cultivate higher understanding as well.
Understandable solutions are good, but great solutions cultivate higher understanding as well. Take more work; but, once you understand how to connect the model of your system to the user’s mental models, it’s easier for you to begin to shape that mental model.
From Ancona et al., Managing for the Future, 2005
From Ancona et al., Managing for the Future, 2005
Add Networked
Add Networked
Separate into slides
Separate into slides
Separate into slides
Separate into slides
Multiple implications
Can also be viewed through various aspects
Typical concern that probably won’t surface or be dealt with. But, the database can help! Could have political issues. Perhaps they won’t talk to each other unless the system does it for them. This problem relates to the need for being flat and flexible .
Could have strategic implications
DB now becoming a decision tool
That’s a really simple example, but it points to the direction I’m going. When a manager says “I wish…” or “That stupid…” it makes me think of the cultural, political and strategic dynamics involved… now I’m also learning to think about ways in which the users interact with the database are influencing those dynamics.
That’s a really simple example, but it points to the direction I’m going. When a manager says “I wish…” or “That stupid…” it makes me think of the cultural, political and strategic dynamics involved… now I’m also learning to think about ways in which the users interact with the database are influencing those dynamics.