From the QF 72 report ...
Firstly, immediately prior to the autopilot disconnect, one of the air data inertial reference units (ADIRUs) started providing erroneous data (spikes) on many parameters to other aircraft systems. The other two ADIRUs continued to function correctly. Secondly, some of the spikes in angle of attack data were not filtered by the flight control computers, and the computers subsequently commanded the pitch-down movements.
The captain reported that he applied back pressure on his sidestick to arrest the pitch-down movement. He said that initially this action seemed to have no effect, but then the aircraft responded to his control input and he commenced recovery to the assigned altitude.
I extracted these two points as they relate to a comment one of our posters in this thread made, (or the RuNe sub forum thread), about length of response time (perceived length of response time???) to his control inputs during a stall. QF 72's captain related to the investigating team a perception of delay between his recovery input and response.
Depending upon the flight regime you are in, and how often you hand fly in that flight regime, you may or may not get the response form the bird that you expect. If you don't get expected response, you may make another input.
What did the PF on AF 447 expect as a response when he took over after noting "Alternate Law" once AP had been diconnected.