Business analysis. This can be used in general for analysis of user requirements, or "business requirements". Presumably business requirements can be seen as a view which summarises the detail of user requirements.
However, business analysis is also used in a somewhat different sense, to mean someone who is only focussed on the profitability of the business.
In fact, there is no conflict between the two.
It may that under a particular HRM regime, only some people have the discretion to discuss the cost-effectiveness of what they are doing.
For example, if people accept pieces of work that are given to them, and are discouraged from questioning the economic use of resources, then it is only people at higher levels than this in the organisation who will be involved in business analysis as directly looking at cost benefits.
Let us ask if it possible to design a business so that cost benefits issues of every single action (down to, say, a keystroke) can be discussed and questioned by everyone in the business. Here, we might want to restrict this to -- anyone who performs an action in the business, e.g. pressing a key, must be allowed to question the economics of what they are doing.
Often this is not the way a system is implemented. Instead, the person who is pressing keys is given a performance standard to meet, e.g. number of keypresses per hour, and has no way to express their concerns about how the system could be designed to run more simply.
Unclear language, no eye contact and not very relevant. Why this short glimpt from a messy office only, why not a lecture?
harshmistress 4 years ago
Good info.TB
meltglass1 4 years ago