8 ms·
They ask for a laundry list of features for all manner of custom scenarios (including those which have never happened or cannot happen). They want it quickly s
by MattGaiser 7y ago
They ask for a laundry list of features for all manner of custom scenarios (including those which have never happened or cannot happen).
They want it quickly so there is no time to plan.
They want it cheaply so there are no resources to test.
They want it according to the drawing they prepared which you then later need to find places to stuff any extra features they ask for later.
They quickly get tired of answering clarifying questions about it and ask developers to "just figure it out." They also don't really care about reliability, or at least that doesn't come up much in discussions.
They insist up and down that their use case is unique and that the way they do things cannot be modified.
They have immensely complex business rules they never wrote down and can't agree on the details of as when the process was done by humans, the answer was up to the human.
So they may not ask for complexity, but that is the end outcome of everything they do ask for.
- jimktrains2 7y agoI've had my best results when I shadow the people doing the work I'm building software to aid and even being trained and go through actually performing said task when possible. It's extremely enlightening to see how things actually happen.
- MattGaiser 7y agoI've done this too and it was great as so many things are usually left out of the spec while priority goes to things which are rarely or never actually done.
- iluvblender 7y agoI can attest to this. As a Technical Director supporting artists the tools I create for them are more effective when I study their process thoroughly and also get my hands dirty. Then design and implement the tool and it becomes my job to manage the complexity. Designing for change is something I keep in mind as well.
- throwaway936482 7y agoYep. This should be step 1 to n of designing software for end users. Understand what the users problems and needs actually are by watching them do their actual job rather than working from a description of what a manager three levels up thinks their job is.
- davidjnelson 7y agoReally good point. I think this is why it’s easier to develop useful software if you are someone who ends up being a user of the software since you have the same problems. You automatically have all the needed empathy.
- Ididntdothis 7y agoSame here. Unfortunately there are a lot of middlemen who want to get in between and filter that information. It’s a constant battle to be allowed to stay in touch with the actual users. It doesn’t help that a lot of devs don’t really want to interact with users feeding the stereotype that developers need to be told what to do.
- LaundroMat 7y agoI once had a retail client wishing for an "in-store Google Maps" that would guide customers to the products they are looking for. "So if I'm looking for pasta, the app should show me on what aisle to find it. That shouldn't be too difficult, should it?", he asked. I asked him how the location of products is stored now. "Is there a system, a database that keeps track of where in the store, on what shelves, product is stocked? Something the app could use so it knows where your pasta can be found?" He didn't understand the question. So I asked him how workers who stock the shelves know where to put what products. There must be a system that gives the workers that information, right? "Oh no", he said, "there is no system. They know through experience and gut-feeling."
- MattGaiser 7y agoMake an app that texts a contractor those questions and lets them drop a pin on a map. Then bill 250,000 a year for the contractor and call it software as a service.
- lmkg 7y agoAs as art project, someone made a camera that, when you snap the shutter, prints out a text description instead of an image. Under the hood, the camera actually submitted the image to Mechanical Turk.
- notyourday 7y agoThat sounds like a super fundable MVP.
- jiveturkey 7y agoand what's wrong with that? the client is asking for an ML solution. or, more basic, a stock person still has to stock the shelves, so they can scan as they stock. or customers themselves can report inventory locations. just tell the customer a random (at first) location for pasta. when you sense they've gotten there, prompt them whether it was there or not. amortized over time, this is an immeasurable fraction of customers that would have to do the inventory work. i get it, you're trying to give an example of an impossible request, of which there are many, but this just isn't one of those.
- MrPatan 7y agoThat's the job. A business software developer's job is to help the people you described overcome those problems. Some have more money than others. Some are smarter than others. Some are better people than others. But ultimately, that's the job.
- ClownWorms 7y agoI would rather just sit back, focus on nice code (even if it is not useful) and let my company bill. I work for a contractor that does government agency work so the longer we can't figure it out, the longer I get paid an absurd amount.
- joe_the_user 7y agoYep, That's the job, it's a huge job taken a whole and to do that job, a variety of systems have arisen; object orientation, functional programming, agile process, etc, etc. All of these tools for helping to decrease complexity. And professions are generally studying at least some of these to "up their chops", so to speak. The thing is, I think the GP was responding to the OP's headline "customers do not ask for software complexity". And the thing is, of course customers ask for a variety things that imply complexity. And, unlike what the OP's discussion, the particular soft approaches that been partly, however much, successful in preventing customer demands from spiraling into unmanageable complex have been ways of dealing with discreet, defined, parts of the development process. The problem with the OP, the article, is that it's a panacea, a vague and general call to make complexity unnecessary with either only a vague explanation of how to do this or an explanation hidden under several layers of rhetoric. "But designing simple software solutions is not simple and requires good principles along with solid experience." I could substitute "supply chains" or "aerospace solutions" and have something plausible sound though I know little about these. Which is to say I don't see OP offering things to make my job (or my former job) easier.
- PaulDavisThe1st 7y ago> And the thing is, of course customers ask for a variety things that imply complexity. That's a claim one could make. If you're going to make it, you need to be ready to defend it. "A implies B" is typically not the case in the sense of "gravity causes objects to fall towards the ground".
- vsareto 7y agoThere's not much to be done here except resort to office politics. Lean on throwing out their architecture and ideas when they say "just figure it out". Lack of direction from them is where you have to assert authority of your expertise - this is where they're giving up control. You essentially need to turn them into a source of simple problem explanation rather than having them give you ideas, unless they can produce code themselves. Determine if dealing with their technical misunderstandings is worth the time invested (few are actually interested in learning technology, but try not to assume).
- NicoJuicy 7y agoDump them, those clients are not the ones you want :) Ps. Raising prices mostly helps
- alephnan 7y agoYou can’t do that when the clients are internal ones.
- NicoJuicy 7y agoThe title says customers and his comment mentions: "They want it cheaply so there are no resources to test." I have never heard of internal customers, I have heared of internal projects ;) . But then the cost are not discussed, deadlines are. And it's still the mission of the product manager to coordinate features to build. In case it's only 1 developer, he has to take the lead and say pro's and cons.
- MattGaiser 7y agoAn internal project budget is to prevent other teams from just endlessly requesting features from the internal developers, i.e. they cannot treat the internal development team as free. It also prevents them from hoarding the developers. Most of the time the billing is just budget shuffling.
- NicoJuicy 7y agoBut it needs input from the product manager. Budget shuffling or not. ( I didn't say work is perfect, but experienced people can make it more doable)
- davidjnelson 7y agoThat’s why communicating a ton and delivering small chunks of fully working functionality helps so much.
- cm2187 7y agoI have no sympathy for that view. I work for a large bank where getting anyone to write any line of code, even for non critical infrastructure, requires a huge amount of energy, frustration, and with anaemic results. Trivial things are overengineered to an absurd level. I estimate that it must take 3 hours of discussions, reports, chasing, conference calls for every minute of code written. And at the same time, while IT cannot deliver even the most trivial changes, they are trying to do everything they can to reduce the productivity of end users to a halt, preventing them from writing any line of code, using any sophisticated tool, locking down the platform, and basically perpetuating copy-pasting, email based processes forever. There is code that I literally prototyped myself in a week and that I am told would take years to rewrite by IT.
- ssss11 7y agoThese 2 things can and do both exist - they both represent a pretty worst-case outcome respectively for users and for IT teams. I feel I’ve worked at both these places.
- cm2187 7y agoI don't disagree. I don't really know anyone working for tech companies, particularly startups. But outside of tech, everyone I know (in various sectors) has the same stories about their IT dept. So I think that this tendency to over engineer and deliver nothing is more than an isolated anecdotical experience.
- sk5t 7y agoTwo things to consider: 1) audit + compliance are running the show 2) the bank not killing the golden goose is more important than anything else.
- TheColorYellow 7y agoThis is a great point too. There is always two sides to this story and often the other side is the budgeting office. Its difficult to see all perspectives in organizations and operations as complex as this. That's generally why management gets paid what it does. Although they're not any more immune to this exact problem...
- PunksATawnyFill 7y agoI disagree. I worked for a couple of big-six consulting firms, and my experience at the last one was that they could be pretty clueless and lazy about determining what the customer really needed. I spent a goodly amount of time preparing a questionnaire about the client's business needs and purposes for doing ad-hoc database queries. None of the questions were leading or simply offered up a feature. They required some thought and would yield useful information. The project manager was baffled by it. NO! he said, clearly flummoxed by this divergence from what apparently was his (and perhaps the firm's) lazy, half-assed approach: Look up all the available products for the customer's task, put all of the features they claim to offer in a big list with checkboxes next to them, and hand it to the client. This is exactly what I was told to do, in the rebuke I got for doing it right. I referred to this as the grocery-list approach. Of COURSE the client is going to create an imaginary need for most of the features and check them off. Who wouldn't? Another great example is "customizable UI." How many thousands of man-years of work have been wasted on this boondoggle?
- BLKNSLVR 7y ago> They quickly get tired of answering clarifying questions about it and ask developers to "just figure it out." This one. I'm primarily familiar with the "internal customer" scenario, and so it becomes uncomfortable to have to go back and forth clarifying details that are crucial to the development of the solution but seem trivial or even entirely inconsequential to the 'customer'. It highlights the size of the knowledge gap between 'customer', who's been doing their process for years and 'developer' who's just finished a project for a completely different aspect of the company and is therefore a blank slate as far as this new project. Another poster mentioned sitting with the people that actually do the process. I can't see a good solution being possible without this - one way or another. That's the role of the Business Analyst isn't it? The translator between requester / user and developer.
- MattGaiser 7y agoThe business analyst can help with translation, but at the end of the day for questions such as, "is the expiration date exclusive or inclusive?" or "what time zone should be used and for which contracts?" he has to ask just like everyone else. There are many questions only relevant to the digital domain.
- thomk 7y agoIs there a title for a person who asks the the technical questions and designs a solution without coding it in your view?
- tonyedgecombe 7y agoThat's the role of the Business Analyst isn't it? That's just one more layer between you and the person doing the work.
- thomk 7y agoI love it when I get the "just figure it out" because then my response is: So you want me to design the software for someone like me? Because that's exactly what I am going to do." That usually gets them to rethink that one. Some Agile here is also a good way out of these kinds of things. Quickly build something they can complain about, then fix it. Either they will start to take responsibility for their software (that is clearly theirs) or they will just keep burning money and that will put an end to it too. However, who you are describing is actually a bad customer. So make sure you get PAID very regularly as you are on this death march and if you ever do not get paid, stop work immediately. Indecision and abdication of responsibility are hallmarks of an incompetent customer.
- tonyedgecombe 7y ago"just figure it out." I always found they assigned the most junior and inexperienced person on their team to liaise with the developers. Eventually I started putting a risk section in the proposal that covered stuff like this. What I found was the more they pushed back on the risks the more likely the risks would occur.
- lunias 7y agoYup. This is how we end up w/ three motorcycles, a sofa, and goose duct taped together when we wish we could have just built a car.