There is a major difference between Windows and GNU/Linux. On Windows it is common, that each program together with all the libraries it depends on is installed in a separate folder. This often leads to a lot of wasted disk space due to libraries being installed multiple times, for each program that uses them.

On Linux, programs are installed following the Filesystem Hierarchy Standard (FHS). This means, that the libraries the programs depend on are all installed in a common dedicated location, so that they are usually only installed once, no matter how many programs use them. Also, programs are built in such a way, that they all use the same version of a certain library. This saves disk space (and RAM at runtime), but has the drawback, that one cannot freely install programs on different partitions or hard disks, at least not without editing system configuration files (for instance /etc/ld.so.conf.d to include the different library folders).

Since the Debian package system was implemented with the FHS in mind, there is, as far as I know, no easy way to install Debian packages to a folder different from the one they were intended to be placed in and have them working without manually moving and editing files afterwards. This is, because paths are often hardcoded at compile time. So even if you install a package to a different folder, for instance by using dpkg --instdir=folder/ package.deb on the command line, the program will still look for its configuration in '/etc', not 'folder/etc', but the config files that were shipped with the package of course were installed to 'folder/etc'... The program will not be added to the menu either, since menu files are supposed to be in '/usr/share applications', not in folder/usr/share/applications.

You can of course manually configure and compile a program from its source code to have it install the binary and data parts wherever you'd like, while still installing configuration files to the FHS compliant locations, but this is something I'd only recommend for advanced users. If you are going to compile from source, have a look at checkinstall, a tool that automatically creates debian packages.

Another option, that was suggested on linuxfromscratch, is to unpack the package to a suitable location and then to create symbolic links to all installed files in the corresponding FHS locations.

Since in the comments you were referring to games: Many games that are not bought through Ubuntu Software Center come as an installer executable, and those can then of course be installed to any folder, usually a subfolder of your home directory. Windows games, which are being run using WINE can also be installed in any directory you want. For wine there exists an environment variable called WINEPREFIX with which you can set up numerous independent WINE folders, each including its own virtual C: drive. Read the WINE man page for more info.

Even if games/programs come as Debian packages, you can look at the package contents in your favorite archive manager. If the game is going to be installed in /opt, you can usually safely install it to a different folder, since /opt is often used as installation location for programs that don't adhere to FHS.