For intra-organization, one way to view private blockchains is to look back to the days of mainframes and the shift to databases. While you technically never need a DB and can get things done with code, DB's are incredibly useful as a general utility because of the baseline features you get by using one. Private blockchains are similar, in that they give you some new features (e.g. sharable DBs) and are much easier to build with as they raise the baseline on how bad a solution can be that is built with them.
While you can have a pretty messed up DB schema, bespoke mainframe solutions can be much worse. Private blockchains are like that (especially when they have smart contracts) -- sure you can really mess up the systems setup but issues that DB's can have like high availability and disaster recovery are 100% commoditized. Also, they demand a higher bar for authorization making them generally as more robust the most hardened DB by default.
That isn't to say that a private blockchain will replace the DB as blockchains can be wild overkill for many domains. A small company that needs a DB doesn't need a blockchain's feature set, but a large company that needs a globally distributed DB for holding a ledger (of anything) would be well served by one. When you're working with a system that by default is BFT, incredibly paranoid about authorization, perfectly replicated and highly available then build a solution gets much easier.
As for the specific problem that they solve, it's the settlement problem: organizations currently hold internal ledgers of truth about what they own but they can't inherently trust other organizations' ledgers of truth about what they own, so we need 3rd parties to settle cross-ledger. Currently, institutions handle this role but private blockchains represent an algorithmic solution.
Buzzword compliance. I predict you will see "Blockchain" products that contain transactions in a Merkle tree as the only technological link to actual blockchains. (R3 have one already, R3 Corda.)
1. They really shine in a p2p architecture where no party trusts each other. But that's not how the financial system works. Banks trust central banks, exchanges and clearing houses, and it is very much a club where players have to be vetted and monitored by a regulator, quite far from the open and wild nature of p2p systems.
2. Market participants need anonymity. Morgan Stanley might not know who hides behind the cryptographic key xxxxx until they do a trade with Goldman Sachs, see that trade appearing in the public ledger and then suddenly they see every single transaction Goldman has done since the dawn of times. Markets need anonymity otherwise market participants can arbitrage you based on what they know you need or plan to do. And the transparency of the public ledger is a fundamental problem.
3. Regulators need transparency. The regulators will need a centralised place where they can put a name against every transaction. That I would thought almost defeats the purpose of the ledger since a traditional transaction log will have to be maintained on the side. Now you have two ledgers.
I remember this excellent blog article explaining when blockchains are pointless and unless I missed something, financial transactions do not meet conditions 3 (Absence of Trust), 4 (Disintermediation).
http://www.multichain.com/blog/2015/11/avoiding-pointless-bl...